Results 1 to 2 of 2

Thread: WebServiceOutboundGateway and WebServiceTemplate

  1. #1
    Join Date
    Jul 2008
    Posts
    21

    Default WebServiceOutboundGateway and WebServiceTemplate

    The WebServiceOutboundGateway uses a WebServiceTemplate but doesn't expose it (there is a getWebServiceTemplate but no setWebServiceTemplate). It's different from JmsSendingMessageHandler with JmsTemplate. I need to disable checkConnectionForFault the property on the WebServiceTemplate, but I can't. What's the reason behind this choice?

  2. #2
    Join Date
    Jun 2012
    Posts
    1

    Default WebServiceOutboundGateway should expose the WebServiceTemplate as a settable property

    We too are having this issue, when dealing with a legacy web service (which cannot be changed) the service does not send a HTTP 500 response and so we want the WebServiceTemplate to check for the fault in the response. Unfortunately we cant access this property. WebServiceOutboundGateway should expose the WebServiceTemplate so it can be overridden.


    Quote Originally Posted by gquintana View Post
    The WebServiceOutboundGateway uses a WebServiceTemplate but doesn't expose it (there is a getWebServiceTemplate but no setWebServiceTemplate). It's different from JmsSendingMessageHandler with JmsTemplate. I need to disable checkConnectionForFault the property on the WebServiceTemplate, but I can't. What's the reason behind this choice?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •