glassfish
  1. glassfish
  2. GLASSFISH-19294

Cannot define multiple endpoints for same EJB WS

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 3.1.2_b05
    • Fix Version/s: 4.0_b75
    • Component/s: web_services
    • Labels:
      None
    • Environment:

      Description

      Trying to define two WS endpoints for the same EJB to work around bug GLASSFISH-19293 . None of the two endpoints is created according to specified endpoint-address-uri.

      Please see attached test case. The endpoint definitions are:

      <ejb>
      <ejb-name>MultEndpntsWS</ejb-name>
      <webservice-endpoint>
      <port-component-name>MultEndpntsWS1</port-component-name>
      <endpoint-address-uri>MultEndpntsWSService/MultEndpntsWS1</endpoint-address-uri>
      <transport-guarantee>NONE</transport-guarantee>
      </webservice-endpoint>
      <webservice-endpoint>
      <port-component-name>MultEndpntsWS2</port-component-name>
      <endpoint-address-uri>MultEndpntsWSService/MultEndpntsWS2</endpoint-address-uri>
      <transport-guarantee>CONFIDENTIAL</transport-guarantee>
      </webservice-endpoint>
      </ejb>

      I can access the wsdl under http://<myserver>:8080/MultEndpntsWSService/MultEndpntsWS?wsdl which seems to be the default URL when no endpoint-address-uri is specified. I cannot access the wsdl under the URLs that I would expect: http://<myserver>:8080/MultEndpntsWSService/MultEndpntsWS1?wsdl and https://<myserver>:8181/MultEndpntsWSService/MultEndpntsWS2?wsdl .

      Checking the deployment guide http://docs.oracle.com/cd/E18930_01/html/821-2417/beass.html#scrolltoc this should be possible (element: webservice-endpoint, required: zero or more).

      Thanks!

      1. MultEndpntsWS.java
        0.3 kB
        stef_esrf

        Activity

        Hide
        Lukas Jungmann added a comment -

        original GLASSFISH-19293 has been already fixed, so this is not needed (it's not supported anyway as port-component-name is defined to be used as a key between EJB and WS endpoint definition hence only one mapping is allowed)

        Show
        Lukas Jungmann added a comment - original GLASSFISH-19293 has been already fixed, so this is not needed (it's not supported anyway as port-component-name is defined to be used as a key between EJB and WS endpoint definition hence only one mapping is allowed)

          People

          • Assignee:
            Lukas Jungmann
            Reporter:
            stef_esrf
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: