Hi, I'm working on a test which has to verify that servicemix-http and cxf-bc components can interoperate (using soap payloads just for now).
So I'm trying to build a route which can be initiated by the test. The route can be described as follows : 1. The test sends a SOAP request to the HTTP SOAP consumer (port 8192, endpoint 'soap') which gets and and routes it to the HTTP SOAP provider (endpoint 'soap2') which pushes it further to a service endpoint listening on localhost:9000. 2. CXF BC consumer listening on localhost:9000 receives it and routes it to CXF BC provider which pushes it further to a service endpoint listening on localhost:9001. 3. HTTP SOAP consumer (port 9001, endpoint 'soap3') gets the soap request and drops it to a jms queue which will be checked by the test. I've gone ahead with implementing this route and it appears that the initial message is received at 1 and eventually dropped to the queue, however I'm seeing that the initiator (the browser in this case) gets HTTP 500 due to one of the exchanges expiring. I've posted some more details here : http://pastebin.com/m7180a31e I have few questions. Is this test route built correctly, given what needs to be tested ? Why the initiator does not get the confirmation like 202/200 back given that an initial soap consumer is listening in the in-only mode ? I think the problem has to do with the fact that a cxfbc:provider expects some response back but the final http soap consumer just drops the in message to the queue so cxfbc:provider fails. Any hints will be appreciated thanks, Sergey -- View this message in context: http://www.nabble.com/servicemix-http-and-cxf-bc-interoperability-tp26110897p26110897.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
