Uploaded image for project: 'Pax Web'
  1. Pax Web
  2. PAXWEB-328

DOMWebXmlParser fails if jsp-file is used

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.1
    • Fix Version/s: 1.1.2, 2.0.0
    • Component/s: War Extender
    • Labels:
      None
    • Environment:
      any

      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)

        Attachments

          Activity

            People

            • Assignee:
              achim_nierbeck Achim Nierbeck
              Reporter:
              mreasy Rico Neubauer
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: