DOMWebXmlParser fails if jsp-file is used

Details

Description

If the web.xml defines a servet to point to a JSP file instead of a servlet-class, parsing fails with a NullPointerException, since servlet-class is expected and fails on setting in WebAppServlet.
Definition in web.xml:
<servlet>
<servlet-name>Thread</servlet-name>
<jsp-file>/jsp/thread.jsp</jsp-file>
</servlet>

leads to:
org.ops4j.lang.NullArgumentException: Servlet class is null.
at org.ops4j.lang.NullArgumentException.validateNotNull(NullArgumentException.java:75)
at org.ops4j.pax.web.extender.war.internal.model.WebAppServlet.setServletClass(WebAppServlet.java:115)
at org.ops4j.pax.web.extender.war.internal.parser.dom.DOMWebXmlParser.parseServlets(DOMWebXmlParser.java:284)
at org.ops4j.pax.web.extender.war.internal.parser.dom.DOMWebXmlParser.parse(DOMWebXmlParser.java:76)
at org.jboss.osgi.webapp.internal.WebXMLParserInterceptor.createWebAppMetadata(WebXMLParserInterceptor.java:82)
at org.jboss.osgi.webapp.internal.WebXMLParserInterceptor.invoke(WebXMLParserInterceptor.java:66)

Achim Nierbeck
added a comment - 09/Dec/11 4:47 PM ok, did some investigation. This one is not trivial
Unfortunately I guess I just can go and ignore those jsp-files for the 1.1.x line.
For the 2.0 I have more freedom in changing

Achim Nierbeck
added a comment - 12/Dec/11 11:02 AM ok, my fault then regarding 2.5 I tried to find out when it was introduced and somehow I had the impression it was 2.5, but never the less it was missing since then then