[
http://issues.ops4j.org/browse/PAXWEB-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566#action_12566
]
Dmitry Sklyut commented on PAXWEB-154:
--------------------------------------
Committed the change. It will only address filters registered with Whiteboard
or directly through WebContainer.
Dispatcher values are defined through init parameters.
Would need to discuss how to handle war extender. Number of design issues that
I don't want to make without further discussion.
> Allow specification of Filter behavior during RequestDispatcher processing
> (i.e. web.xml filter-mapping/dispatcher)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: PAXWEB-154
> URL: http://issues.ops4j.org/browse/PAXWEB-154
> Project: Pax Web
> Issue Type: New Feature
> Components: Web Container, Whiteboard Extender
> Affects Versions: 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.3.0, 0.3.1, 0.4.0, 0.4.1,
> 0.5.0, 0.5.1, 0.5.2, 0.6.0, 0.7.0
> Reporter: Dmitry Sklyut
> Assignee: Dmitry Sklyut
>
> Currently there is no way to define filter behavior during RequestDispatcher
> processing.
> For example:
> in web.xml one can define filter mapping as
> <filter-mapping>
> <filter-name>Test</filter-name>
> <url-pattern>/test/*</url-pattern>
> <servlet-name>SomeServlet</servlet-name>
> <dispatcher>REQUEST</dispatcher>
> <dispatcher>FORWARD</dispatcher>
> </filter-mapping>
> This feature is only available in servlet spec 2.4 and above
--
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
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
