Spring Integration
  1. Spring Integration
  2. INT-2695

In org.springframework.integration.ws.MarshallingWebServiceOutboundGateway the field 'uri' doesn't work the same way the 'deafultUri' works in org.springframework.ws.client.core.WebServiceTemplate

    Details

      Description

      In WebServiceTemplate the field 'defaultUri' can understand URI for both HTTP (i.e. http://abc.com/) and JMS (i.e jms:MY.TOPIC.JNDI?messageType=TEXT_MESSAGE). But in org.springframework.integration.ws.MarshallingWebServiceOutboundGateway
      the field 'uri' only understands HTTP URI. If one needs to use JMS URI then he needs to implement his own org.springframework.ws.client.support.destination.DestinationProvider. But this is not properly documented. It would be great if we could:

      1) make 'uri' field understands JMS (or any other) URIs
      2) update the documentation so that users can easily find out that they need to implement DestinationProvider

        Issue Links

          Activity

          Hide
          Mark Fisher added a comment -

          We should at least add a note in the documentation for 2.2 (saying that the workaround is to add a DestinationProvider) and then if we need to we can push the long-term fix to 3.0

          Feel free to create new JIRAs as necessary.

          Show
          Mark Fisher added a comment - We should at least add a note in the documentation for 2.2 (saying that the workaround is to add a DestinationProvider) and then if we need to we can push the long-term fix to 3.0 Feel free to create new JIRAs as necessary.
          Hide
          Artem Bilan added a comment -

          If we take a look into Spring-WS Manual: http://static.springsource.org/spring-ws/sites/2.0/reference/html/client.html#client-transports
          We'll be able to make conclusion, that our org.springframework.integration.ws.AbstractWebServiceOutboundGateway$HttpUrlTemplate should be redesigned to support all transport and uriVariableExpressions as well as it is done for HTTP.
          It allows to SI fully to support SWS.
          IMO it is a prototype for new improvement issue.

          Show
          Artem Bilan added a comment - If we take a look into Spring-WS Manual: http://static.springsource.org/spring-ws/sites/2.0/reference/html/client.html#client-transports We'll be able to make conclusion, that our org.springframework.integration.ws.AbstractWebServiceOutboundGateway$HttpUrlTemplate should be redesigned to support all transport and uriVariableExpressions as well as it is done for HTTP. It allows to SI fully to support SWS. IMO it is a prototype for new improvement issue.
          Show
          Gary Russell added a comment - Issued PR: https://github.com/SpringSource/spring-integration/pull/613

            People

            • Assignee:
              Gary Russell
              Reporter:
              Zahidul Islam
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: