[
https://issues.apache.org/jira/browse/WW-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508627#comment-13508627
]
Daniel Le Berre commented on WW-3933:
-------------------------------------
The only reliable resource on the topic is I guess the Servlet 3.0
specification, chapter 8.2.1 "Modularity of web.xml" page 65.
The idea would be to have a default filter name for struts 2 default filter in
the fragment (e.g. org.apache.struts2.filter) with a default class and filter
mapping.
The definition of another filter with the same name in the web.xml should take
precedence on the fragment:
"4. The web.xml of the web application has the highest precedence when resolving
conflicts between the web.xml, web-fragment.xml and annotations." page 73 of
the Servlet 3.0 specification.
> Provide web-fragment.xml for easier deployment on Servlet 3.0 compliant
> containers
> ----------------------------------------------------------------------------------
>
> Key: WW-3933
> URL: https://issues.apache.org/jira/browse/WW-3933
> Project: Struts 2
> Issue Type: Improvement
> Components: Dispatch Filter
> Affects Versions: 2.3.7
> Reporter: Daniel Le Berre
> Priority: Minor
> Fix For: 2.5.x
>
>
> Servlet 3.0 specification includes the possibility for libraries to ship
> web-fragment.xml files in their META-INF directory to contribute some
> declarations to the main web.xml file.
> Struts 2 only requires the declaration of a filter in the web.xml file to
> work. When building Servlet 3.0 webapp, the web.xml file is often not used at
> all.
> It would be nice to ship a web-fragment.xml file in struts 2 that declares
> the PrepareAndExecute filter to simplify the use of the framework on a
> servlet 3.0 stack.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
