[jbossws-issues] [JBoss JIRA] Updated: (JBWS-1854) Cannot deploy nested JSE endpoint in SAR

[Thomas Diesler (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBWS-1854?page=all ]

Thomas Diesler updated JBWS-1854:
---------------------------------

    Fix Version/s:     (was: jbossws-2.0.1.SP2)

> Cannot deploy nested JSE endpoint in SAR
> ----------------------------------------
>
>                 Key: JBWS-1854
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1854
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>
> We have an issue, JBoss Portal WSRP service doesn't deploy in Branch 
> 4.2, the issue seems to be related to the WS changes.
> I noticed that in jbossws.sar/META-INF/jboss-service.xml the following 
> has been removed:
>     <!--
>       A deployer service for JSE endpoints that are nested in service 
> archives (sar).
>     -->
>     <mbean name="jboss.ws:service=DeployerInterceptorNestedJSE" 
> code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
>        <depends optional-attribute-name="MainDeployer" 
> proxy-type="attribute">jboss.system:service=MainDeployer</depends>
>        <depends>jboss.ws:service=WebServiceDeployerJSE</depends>
>     </mbean>
> We do have a jse included into a sar and the end result is that the WSRP 
> service doesn't start with the following error message:
> --- Packages waiting for a deployer ---
> org.jboss.deployment.DeploymentInfo at be17fae3 { 
> url=file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse 
> }
>    deployer: null
>    status: Starting
>    state: INIT_WAITING_DEPLOYER
>    watch: 
> file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
>    altDD: null
>    lastDeployed: 1192192027649
>    lastModified: 1192191975000
>    mbeans:
> I wanted to let you know. I didn't investigate more than that, other 
> than trying to find the corresponding class for the deployer, but it 
> seems that it's not in the codebase anymore.

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