[jbossws-issues] [JBoss JIRA] Updated: (JBWS-1133) Unpacked JSR-181 POJO deployment fails for subsquent deployment.

Darran Lofthouse (JIRA) jira-events at lists.jboss.org
Sat May 5 12:41:52 EDT 2007


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

Darran Lofthouse updated JBWS-1133:
-----------------------------------

    Fix Version/s: jbossws-2.0.1
                       (was: jbossws-2.0.0)

Still one issue to be respolved as this fix causes the generated war of an EJB deployment to be incorrectly deployed as a new web service deployment.  

Some indicator is required to stop the isWebserviceDeployment call on the generated web app.

> Unpacked JSR-181 POJO deployment fails for subsquent deployment.
> ----------------------------------------------------------------
>
>                 Key: JBWS-1133
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1133
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jaxws
>    Affects Versions:  jbossws-1.0.1
>            Reporter: Darran Lofthouse
>         Assigned To: Darran Lofthouse
>             Fix For: jbossws-2.0.1
>
>
> Unpacked JSR-181 POJO deployments are not deployed correctly for subsequent server starts.
> This is because when this is first deployed the web.xml which is part of the deployment is modified so that the JBossServiceEndpointServlet servlet is used.  
> On subsequent deployments the web.xml is parsed but because all of the servlet classes have been replaced with the JBossServiceEndpointServlet it is JBossServiceEndpointServlet that is checked for annotations instead of the endpoint class.

-- 
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

        



More information about the jbossws-issues mailing list