ODE
  1. ODE
  2. ODE-347

Add wsdlLocation attribute to Metadata element of endpoint reference

    Details

      Description

      The WSDL location is needed by a partner in a callback message exchange pattern. The wsdlLocation attribute defined in the http://www.w3.org/2006/01/wsdl-instance schema is an appropriate way to supply this information.

      Attached is a patch to add this information to endpoint references generated from the the partner links role acting in a callback capacity.

        Activity

        Hide
        Matthieu Riou added a comment -

        Isn't that going to make your problem worse given that the provided URL will be the one for the WSDL rewritten by Axis2?

        Show
        Matthieu Riou added a comment - Isn't that going to make your problem worse given that the provided URL will be the one for the WSDL rewritten by Axis2?
        Hide
        Callum Haig added a comment - - edited

        Hi Matthieu,

        Until the public WSDL location yields a file which truly describes the
        services/ports rendered in endpoint references provided to third
        parties my suggestion won't help. However in principle I believe the
        WSDL location should be made available in this way (CXF depends on it in calls such as
        EndpointReferenceUtils.getWSDLLocation(EndpointReferenceType
        callback), and other frameworks may too).

        There are two disctinct problems, and perhaps this change should only
        accompany the addressing of the other issue (which is synchronising
        the service details appearing in the WSDL and those in endpoint
        references provided to third parties).

        Regards,
        Callum.

        Show
        Callum Haig added a comment - - edited Hi Matthieu, Until the public WSDL location yields a file which truly describes the services/ports rendered in endpoint references provided to third parties my suggestion won't help. However in principle I believe the WSDL location should be made available in this way (CXF depends on it in calls such as EndpointReferenceUtils.getWSDLLocation(EndpointReferenceType callback), and other frameworks may too). There are two disctinct problems, and perhaps this change should only accompany the addressing of the other issue (which is synchronising the service details appearing in the WSDL and those in endpoint references provided to third parties). Regards, Callum.
        Hide
        Matthieu Riou added a comment -

        The way we're sending EPRs so far in ODE is by using WS-Addressing. I'm not sure using the WSDL location is a very common pattern...

        Show
        Matthieu Riou added a comment - The way we're sending EPRs so far in ODE is by using WS-Addressing. I'm not sure using the WSDL location is a very common pattern...

          People

          • Assignee:
            Unassigned
            Reporter:
            Callum Haig
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development