I managed to get a similar scenario going, with the following configuration:
cxfbc configuration:
<cxfbc:consumer wsdl="classpath:wsdl/DataGateway.wsdl"
targetService="stake:dgw-request-response"
endpoint="DataMaintenanceJBISOAPPort"
service="dgw:DataMaintenanceJBIService"/>
<cxfbc:provider wsdl="classpath:wsdl/DataGateway.wsdl"
locationURI="http://localhost:7001/gateway/services/DataMaintenanceService";
endpoint="DataMaintenanceSOAPPort"
service="dgw:DataMaintenanceService">
jms configuration:
<jms:endpoint service="stake:dgw-request-response"
endpoint="endpoint"
role="provider"
destinationStyle="queue"
jmsProviderDestinationName="query.request"
jmsProviderReplyToName="query.response"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
connectionFactory="#connectionFactory" />
<jms:endpoint service="stake:dgw-request-response-reader"
targetService="dgw:DataMaintenanceService"
endpoint="endpoint"
role="consumer"
destinationStyle="queue"
jmsProviderDestinationName="query.request"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
jmsProviderReplyToName="query.response"
defaultOperation="dgw:query"
connectionFactory="#connectionFactory" />
Like everyone else, I struggled to find the correct reply destination
attribute that would work. jmsProviderReplyToName worked for me.
--
View this message in context:
http://www.nabble.com/Configuring-jms-and-web-service-flow-tp18627595p18717822.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
