[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2246) NPE deploying web services in service archive in CR1 release

Richard Opalka (JIRA) jira-events at lists.jboss.org
Mon Oct 6 04:21:20 EDT 2008


    [ https://jira.jboss.org/jira/browse/JBWS-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12432576#action_12432576 ] 

Richard Opalka commented on JBWS-2246:
--------------------------------------

The problem is there are deployment aspects that are dependent on Tomcat runtime.
These aspects needs to be executed in Servlet lifecycle methods rather than in deployes chain.

> NPE deploying web services in service archive in CR1 release
> ------------------------------------------------------------
>
>                 Key: JBWS-2246
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2246
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-integration
>    Affects Versions:  jbossws-native-3.0.2
>         Environment: Vanilla JBossAS5.0.0.CR1 release on Fedora 9/Sun JDK 1.5.0_12-b0
>            Reporter: Andrew Dinn
>            Assignee: Richard Opalka
>             Fix For: jbossws-native-3.0.4
>
>
> I am trying to deploy a sar in AS5.0.0.CR1 which includes several war files. These wars include JaxWS SEI classes anotated with WebService annotations. The AS is using the bundled version of JBossWS Native.
> The war file deployment breaks if the sar is deployed before starting JBoss AS. This is because the WS KernelLocator bean has not been intiialized. This is supposed to happen via bean injection according to the bean definition in jbossws-container-beans.xml located in server//deploy. However, the war file is processed (by an instance of JaxWSDeployerHookPreJSE) before the value is injected. The deployer tries to look up the wsf runtime via the kernel and receives a null pointer exception (stack trace as follows):
> . . .
> Caused by: java.lang.NullPointerException
> at org.jboss.wsf.common.KernelAwareSPIFactory.getKernelProvidedSPI(KernelAwareSPIFactory.java:40)
> at org.jboss.wsf.framework.DefaultWSFRuntimeLocator.locateRuntime(DefaultWSFRuntimeLocator.java:36)
> at org.jboss.wsf.container.jboss50.deployer.AbstractDeployerHook.getWsfRuntime(AbstractDeployerHook.java:59)
> at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:86)
> at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:62)
> at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174)
> ... 18 more 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbossws-issues mailing list