DOMWebXmlParser fails if jsp-file is used ----------------------------------------- Key: JBOSGI-504 URL: https://issues.jboss.org/browse/JBOSGI-504 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-webapp Affects Versions: JBossOSGi 1.0.0 Reporter: Rico Neubauer Assignee: Thomas Diesler OSGi-deployment fails if web.xml defines a jsp-file entry. This is actually a bug in the used pax-web component. Opened up here: http://team.ops4j.org/browse/PAXWEB-328 This is for information, maybe thinking about a workaround and to upgrade, once it is fixed. Stacktrace including JBoss classes as well: [org.jboss.msc.service] (MSC service thread 1-7) MSC00002: Invocation of listener "org.jboss.as.osgi.deployment.BundleStartTracker$1@6d5535b7" failed: 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) at org.jboss.osgi.deployment.interceptor.AbstractLifecycleInterceptorService.handleStateChange(AbstractLifecycleInterceptorService.java:281) [jbosgi-deployment-1.0.10.jar:] at org.jboss.osgi.framework.internal.LifecycleInterceptorPlugin.handleStateChange(LifecycleInterceptorPlugin.java:125) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:183) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:172) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:282) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144) [jboss-as-osgi-service-7.1.0.Beta1.jar:] at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119) [jboss-as-osgi-service-7.1.0.Beta1.jar:] at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952) [jboss-msc-1.0.1.GA.jar:] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira