[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2588) Webservice deployed within EAR fails but war file only deployment successful

[Martin Eigenbrodt (JIRA)]

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

Martin Eigenbrodt commented on JBWS-2588:
-----------------------------------------

Isn't this stil a bug? A JEE 5 AS should not rely on an application.xml

> Webservice deployed within EAR fails but war file only deployment successful
> ----------------------------------------------------------------------------
>
>                 Key: JBWS-2588
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2588
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: Currently using JBoss AS 5.0.1GA on Windows XP JRE 1.6.11
>            Reporter: Paul Smith
>         Attachments: WebServiceEAR.zip
>
>
> I have created a simple annotated web service and it added it to a WAR. If this is deployed from eclipse to the JBoss server it deploys correctly and is accessible. If the the same WAR is then contained within an EAR file and deployed. The deployment fails with the following:
> 12:41:07,967 ERROR [[TestWs]] Allocate exception for servlet TestWs
> javax.xml.ws.WebServiceException: Cannot obtain endpoint for: jboss.ws:context=/WebService,endpoint=TestWs
> 	at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initEndpoint(AbstractEndpointServlet.java:153)
> 	at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initServiceEndpoint(AbstractEndpointServlet.java:124)
> 	at org.jboss.wsf.common.servlet.AbstractEndpointServlet.init(AbstractEndpointServlet.java:72)
> 	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048)
> 	at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
> 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
> 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> 	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> 	at java.lang.Thread.run(Thread.java:619)

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