glassfish
  1. glassfish
  2. GLASSFISH-20658

@WebService and @Stateless not showing endpoint in GlassFish 4.0 admin console

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 4.0
    • Fix Version/s: future release
    • Component/s: admin_gui
    • Labels:
      None

      Description

      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 :

      @WebService
      public class HelloServletEndpoint {
      
          public String saySomethingServlet(String something) {
              return "The HelloServletEndpoint is saying : " + something;
          }
      }
      
      @WebService
      @Stateless
      public class HelloEJBEndpoint {
      
          public String saySomethingEJB(String something) {
              return "The HelloEJBEndpoint is saying : " + something;
          }
      }
      

      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

        Activity

        Hide
        teefal added a comment -

        Thank you for the part I was missing:

        http://localhost:8080/HelloEJBEndpointService/HelloEJBEndpoint?wsdl

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

        Show
        teefal added a comment - Thank you for the part I was missing: http://localhost:8080/HelloEJBEndpointService/HelloEJBEndpoint?wsdl 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!)
        Hide
        Bruno Borges added a comment -

        Hi Antonio,

        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?

        Show
        Bruno Borges added a comment - Hi Antonio, 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?

          People

          • Assignee:
            Anissa Lam
            Reporter:
            Antonio Goncalves
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: