https://issues.apache.org/bugzilla/show_bug.cgi?id=52138
Bug #: 52138
Summary: global web.xml servlet-mappings are not used when
additional mappings are defined in app web.xml
Product: Tomcat 7
Version: 7.0.22
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: james_defel...@elementk.com
Classification: Unclassified
In my application web.xml I define a servlet-mapping for a new extension:
<servlet-mapping>
<servlet-name>jsp</servlet-name>
<url-pattern>*.jss</url-pattern>
</servlet-mapping>
I have not modified, in any way, the global web.xml file.
The application context is loaded just fine, but .jsp files are not handled by
the JspServlet (which is declared in global web.xml). The end result being
that the JSP source code is served to a web client instead of HTML generated by
a compiled jsp class.
.jsp files are compiled if I add the following to my web.xml:
<servlet-mapping>
<servlet-name>jsp</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>
However, this seems redundant since that mapping is declared already in the
global web.xml file. My expectation was that the global mappings would be
merged with the application mappings at deploy time -- which does not seem to
be happening in this case.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
