Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>From what I gather from reading the <a href="http://static.springframework.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/transport/jms/WebServiceMessageDrivenBean.html" rel="nofollow noreferrer">javadocs</a> it looks like this allows a Spring <a href="http://static.springframework.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/transport/WebServiceMessageReceiver.html" rel="nofollow noreferrer">WebServiceMessageReceiver</a> to be invoked using a JMS client instead of a web services client. Hopefully that's right, because the rest of this is based on that assumption.</p> <p>The basics of is should match with how you create a regular Spring message driven bean. There is a little bit of documentation on how to do that in the <a href="http://static.springframework.org/spring/docs/2.5.x/reference/ejb.html#ejb-implementation" rel="nofollow noreferrer">Spring Reference Manual</a>. Also see the <a href="http://static.springframework.org/spring/docs/2.5.x/api/org/springframework/ejb/support/AbstractEnterpriseBean.html?is-external=true" rel="nofollow noreferrer">AbstractEnterpriseBean Javadoc</a> for some additional information about how the Spring context is retrieved. </p> <p>The extra configuration required for a WebServiceMessageDrivenBean appear to be a <a href="http://java.sun.com/javaee/5/docs/api/javax/jms/ConnectionFactory.html?is-external=true" rel="nofollow noreferrer">ConnectionFactory</a>, a <a href="http://static.springframework.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/WebServiceMessageFactory.html" rel="nofollow noreferrer">WebServiceMessageFactory</a>, and your <a href="http://static.springframework.org/spring-ws/sites/1.5/apidocs/org/springframework/ws/transport/WebServiceMessageReceiver.html" rel="nofollow noreferrer">WebServiceMessageReceiver</a>. These need to use the bean names specified in the Javadoc for the WebServiceMessageDrivenBean. The bean names are "connectionFactory", "messageFactory", and "messageReceiver" respectively. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload