[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2246) NPE deploying web services in service archive in CR1 release
[
https://jira.jboss.org/jira/browse/JBWS-2246?page=com.atlassian.jira.plug...
]
Andrew Dinn commented on JBWS-2246:
-----------------------------------
I am not convinced this is an AS issue. It appears to me to be a straightforwrad bootstrap
issue in JBossWS. The problem is that the JaxWS deployer hook is relying upon injection to
install the kernel locator. This would be ok if execution of the deployer hook code could
be made to wait upon completion of the bean injection. However, currently the AS is _not_
designed to allow invocation of deployers to depend upon deployment of deployed components
(not to mention a deployment from the service the deployer belongs to). Handing this off
to the AS is equivalent to asking for that design decision to be reversed. Is this a
sensible thing to do? (perhaps Ales would like to comment on this :-) If not then WS needs
to make sure its deployers can run without relying upon its own deployments having
completed.
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)
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
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