aspose file tools*
The moose likes Web Services and the fly likes Cannot deploy web service in GlassFish using together @WebserviceProvider and @Stateless Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Cannot deploy web service in GlassFish using together @WebserviceProvider and @Stateless" Watch "Cannot deploy web service in GlassFish using together @WebserviceProvider and @Stateless" New topic
Author

Cannot deploy web service in GlassFish using together @WebserviceProvider and @Stateless

Mike Abramov
Greenhorn

Joined: Nov 05, 2011
Posts: 3
I tried to deploy in GlassFish JAX-WS web service,
Here is a snippet of class were the web service is defined. Pay attention that I use @WebServiceProvider

The problem is about the deploying the service in GlassFish (3.1.2.2) . For some reason it seems that it the server treats like EJB but not service endpoint.
I made such conclusion based on the GlassFish log :

[#|2012-09-08T16:39:15.682-0400|INFO|glassfish3.1.2|javax.enterprise.system.container.ejb.com.sun.ejb.containers|_ThreadID=20;_ThreadName=Thread-2;|EJB5181:Portable JNDI names for EJB HelloWorldEJBWS: [java:global/JAX-WS_GreetingEJBMutualAuthProvider/HelloWorldEJBWS, java:global/JAX-WS_GreetingEJBMutualAuthProvider/HelloWorldEJBWS!javax.xml.ws.Provider]|#]

[#|2012-09-08T16:39:15.792-0400|INFO|glassfish3.1.2|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=20;_ThreadName=Thread-2;|WS00019: EJB Endpoint deployed
JAX-WS_GreetingEJBMutualAuthProvider listening at address at http://localhost:8088/HelloWorldWSService/com.ivan.wsejb.provider.HelloWorldEJBWS|#]

For comparison I provide the log when I deployed the service using @WebService but not @WebServiceProvider

[#|2012-09-08T16:41:50.514-0400|INFO|glassfish3.1.2|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=22;_ThreadName=Thread-2;|WS00019: EJB Endpoint deployed
JAX-WS_GreetingEJBMutualAuth listening at address at http://localhost:8088/HelloWorldEJBWSService/HelloWorldEJBWS|#]


and here is snipped of the code when I apply @WebService

Did I do something wrong ?
Mike Abramov
Greenhorn

Joined: Nov 05, 2011
Posts: 3
I did everything right, but was mislead by GlassFish. It could be a a bug...
When I deploy web service with endpoint implemented as servlet (second case) in the console I can see endpoint, but in case with endpoint implemented as EJB the endpoint did not appear in the console. But I could access the WSDL with a link http://ABRAMOV1:8088/HelloWorldWSService/com.ivan.wsejb.provider.HelloWorldEJBWS?wsdl and ultimately tested web service with the client
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Cannot deploy web service in GlassFish using together @WebserviceProvider and @Stateless
 
Similar Threads
cant load the admin console in glassfish v3
hibernate glassfish no security manager: RMI class loader disabled
Glassfish 3 and Remote EJB Access
This bundle has no bean of name error on GlassFish 2.1.1
hibernate glassfish no security manager: RMI class loader disabled