title: Spring WebserviceTemplate uses JMS as messageSender
body: <p>In one of the projects I worked on the architect used Spring WebserviceTemplate in most of the backend services and its definition in xml config is like:</p>
  
  <pre><code>&lt;bean id="someservice" class="org.springframework.ws.client.core.WebServiceTemplate"&gt;
    &lt;property name="messageSender"&gt;
      &lt;bean class="JmsMessageSender"&gt;
  ....
  </code></pre>
  
  <p></p>
  
  <p>In this configuration, the JmsMessageSender (<code>org.springframework.ws.transport.jms.JmsMessageSender</code>) extends WebserviceMessageSender  and its underlying infrastructure is Solace the message broker.</p>
  
  <p>As I understand that the webservice is for synchronous communication, the above should be using the JMS request/response model only - there is no way to use Spring's WebserviceTemplate for JMS's asynchronous model. </p>
  
  <p>Is it correct? However if we start a new project for a similar purpose, wouldn't it be better to use the more simple and elegant RestfulTemplate+Json+Jackson, as opposed to SOAP+JAXB solution as above?</p>