[GLASSFISH-20658] @WebService and @Stateless not showing endpoint in GlassFish 4.0 admin console Created: 24/Jun/13 Updated: 12/Dec/16
|Fix Version/s:||future release|
|Reporter:||Antonio Goncalves||Assignee:||Anissa Lam|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Tags:||admin-gui, stateless, webservice|
I wrote two very basic SOAP Web Services (https://github.com/agoncal/agoncal-sample-jaxws/tree/master/01-EndPoints) : one using a servlet endpoint and another one using an EJB endpoint :
I've packaged them in a war file and deployed the war into a GlassFish 4.0 instance (a full profile). When I check the admin console, I can view the servlet endpoint (test it and see the generated WSDL) but it does not work with the EJB endpoint (see the attached image). Both WSDLs are available though on the following URLs :
Looks like this is a bug in the UI
|Comment by Bruno Borges [ 05/Feb/14 ]|
The reason to have <EJBName> as context-root for the @Stateless @WebService is for the case when they are deployed inside EJB modules in EAR files (Java EE 5), where there's no Web access (and so, no context-root).
I wonder though if there's anything in the specification of Java EE 6 that clarifies how the context-root of the EJB WebService should behave in the case it is deployed inside a single WAR instead of an EJB module.
Which specification should we be looking at? EJB or JAX-WS?
|Comment by teefal [ 12/Dec/16 ]|
Thank you for the part I was missing:
I was leaving off the HelloEJBEndpointService part, so couldn't get a WSDL after adding Stateless.
(was actually reading your book when I got the idea to try this ... great books!)