[
http://issues.ops4j.org/browse/PAXWEB-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11980#action_11980
]
Alin Dreghiciu commented on PAXWEB-125:
---------------------------------------
Indeed this is a bug. The section SRV.6.2.4 of Servlet specs 2.5 (I suppose is
the same in earlier versions) specify that the filers should be invoked and
placed in the chain according to the order in <filter-mapping> document, where
first are <url-pattern> and then <servlet-name> mappings.
> Filters exececuted in <filter> order rather than <filter-mapping> order
> -----------------------------------------------------------------------
>
> Key: PAXWEB-125
> URL: http://issues.ops4j.org/browse/PAXWEB-125
> Project: Pax Web
> Issue Type: Bug
> Reporter: David Holroyd
> Assignee: Alin Dreghiciu
>
> I have a webapp I've been developing in Jetty outside of OSGi. Now trying to
> convert it to an OSGi bundle using PAX tooling, I found that the declared
> filters were not running in the expected order.
> In the debugger, I noticed that the order of filters in Jetty's filter chain
> corresponds to the order of the <filter> elements in web.xml, rather than the
> order of the <filter-mapping> elements, as expected.
> By reorganising web.xml, I was able to continue on to debugging the next lot
> of NCDF errors :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
