Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-2246

NPE deploying web services in service archive in CR1 release

    XMLWordPrintable

Details

    Description

      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

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBWS-2271 TomcatDeployer / MainDeployer: Could not start deployment

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBWS-2264 NPE when web services are shut down

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBWS-2332 Review and fix JBossWS integration with JBoss AS 5x

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBAS-5732 Deployment of @WebService fails

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ropalka Richard Opalka
              rhn-engineering-adinn Andrew Dinn
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: