From: Dannes W. <di...@ex...> - 2009-12-20 20:55:57
|
On 20 Dec 2009, at 21:41 , Andrzej Jan Taramina wrote: > This makes no sense to me....why would we leave something in web.xml that is optional, and have it cause a series of exception traces in the logs (which can be disconcerting) if a user elects to not include the optional feature? Ah, right. You have the wrong perspective here. The web interfaces (and thus the cocoon stuff) are not part of the exist-db core, they hook into the core. For example, when running in embedded mode (interactive client), you can not use this code. > In any case, not a big deal for me...I post-process the web.xml file and just added some xslt code to remove all Cocoon references when we build our custom war....so that solves it for me. ;-) :-) probably we'll reconsider these cocoon stuff in web.xml ...... (e.g. move to documentation or alternative web.xml) Kind regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |