I was expecting that CXF would enable the JMS Feature automatically when
discovering JMS transport in the WSDL, as CXF does for security features
when discovering a security policy in the WSDL. Am I wrong? Are there two
different implementations in CXF handling JMS transport?
I prefer WSDL automatic configuration much more than (custom) direct
configuration in my beans.xml.
Well, if I want to make my address configurable I still can use the
"address" attribute, which I do for the client side (in my case) but my
server should simply take the address from the wsdl (which is working as
expected).
Here is a code sample for my client:
<jaxws:client id="jmsTransport"
xmlns:serviceNamespace="http://services.talend.org/CRMService";
serviceName="serviceNamespace:CRMServiceProvider"
endpointName="serviceNamespace:CRMServiceJMSQueuePort"
serviceClass="org.talend.services.crmservice.CRMService"
wsdlLocation="WEB-INF/wsdl/CRMService.wsdl" address="${jms.address}"
/>
--
View this message in context:
http://cxf.547215.n5.nabble.com/JMS-Topic-Support-with-Response-is-not-working-tp5732525p5732554.html
Sent from the cxf-user mailing list archive at Nabble.com.
