Servlet 2.3 web.xml files are order-specific. If you put things in a different order, the behavior is undefined. Some containers report an error. Some containers silently ignore things out of order. Some handle it correctly.
Refer to http://java.sun.com/dtd/web-app_2_3.dtd for the order, but this is the heart of it: <!ELEMENT web-app (icon?, display-name?, description?, distributable?, context-param*, filter*, filter-mapping*, listener*, servlet*, servlet-mapping*, session-config?, mime-mapping*, welcome-file-list?, error-page*, taglib*, resource-env-ref*, resource-ref*, security-constraint*, login-config?, security-role*, env-entry*, ejb-ref*, ejb-local-ref*)> On 12/19/06, Renzo Tomaselli <[EMAIL PROTECTED]> wrote:
Hi, for the purpose of softly switching to Trinidad, I just reconfigured an existing application - Tomahawk & Facelets based - to be Trinidad-ready. I did this by adding proper entries to web.xml and faces-config.xml, then adding the latest jar pairs for Trinidad. No source modifications. I was fairly surprised to notice that result depends on element ordering within web.xml. Specifically, if appending all new Trinidad stuff at the end, then I get an error at application startup: no Trinidad filter was found, and no rendering context as well. After moving all to the beginning, application starts, although several things do not work as before: I still have to investigate further, but first I'd like to collect a few comments about the ordering topic, since I neve saw it on any document - either Trinidad or Facelets based. Thanks -- Renzo
