ops4j / org.ops4j.pax.web

OSGi R7 Http Service, Whiteboard and Web Applications (OSGi CMPN Release chapters 102, 140 and 128) implementation using Jetty 9, Tomcat 9 or Undertow 2.
https://ops4j1.jira.com/wiki/display/paxweb/Pax+Web
Other
146 stars 184 forks source link

War extender only supports ".jsp" extension for JSPs [PAXWEB-208] #540

Closed ops4j-issues closed 14 years ago

ops4j-issues commented 14 years ago

Bryan Keller created PAXWEB-208

The Pax-Web War extender only supports the ".jsp" extension for JSP files. Other extensions are commonly used, especially ".jspx" for the newer JSP XML format. Jetty standalone supports the following by default (see http://docs.codehaus.org/display/JETTY/webdefault.xml)::) .jsp, .jspf, .jspx, .xsp, .JSP, .JSPF, .JSPX, .XSP.

The relevant line of code is in org.ops4j.pax.web.extender.war.internal.RegisterWebAppVisitorWC.java, line 155.

m_webContainer.registerJsps(
new String[] { "*.jsp" }

,
m_httpContext
);

should be:

m_webContainer.registerJsps(
new String[] { ".jsp", ".jspx", ".jspf", ".xsp" }

, //etc. others ...
m_httpContext
);


Affects: 0.7.2 Fixed in: 0.8.0 Votes: 0, Watches: 0

ops4j-issues commented 14 years ago

Achim Nierbeck commented

I created a branch at github:

http://github.com/ops4j/org.ops4j.pax.web/tree/webSecureContext

this fix is also contained within this branch

ops4j-issues commented 14 years ago

Achim Nierbeck commented

is fixed and can be found in the master branche at github
http://github.com/ops4j/org.ops4j.pax.web