Hi All, I am trying to expose an asynchronous webservice via ESB but having some issues with WS-Addressing.
I have made a asynchornous webservice and client which works fine if I test it in point to point model. However when I am trying to expose it via ESB - so that the client calls the ESB endpoint instead of direct service endpoint, iam running into issues. The ESB requires WS-Addressing to be enabled at service end so that it could handle the async response. I have implemented it and when I run the client to call ESB endpoint, the ESB acts as a client and calls my WS-Addressing enabled service and tries to consume the response but it fails- the error message is " Message does not contain a valid SOAP Reply Identifier." I see that the the cxf services sends 2 responses back to ESB -- The 1st response contains anonymous at the "TO" field with empty soap:Body ( Please see below) and the second response is the actual proper response. <To xmlns="http://www.w3.org/2005/08/addressing";>http://www.w3.org/2005/08/addressing/anonymous</To> <ReplyTo xmlns="http://www.w3.org/2005/08/addressing";> <Address>http://www.w3.org/2005/08/addressing/none</Address> </ReplyTo> I think ESB is not able to understand the 1st response that is being sent. Can you please help me out on why CXF sends 2 responses? Please not that Synchronous CXF services via ESB works fine. Below are some configuration I have used. -- @Addressing(enabled = true, required = false, responses = Responses.NON_ANONYMOUS) <wsa:addressing xmlns:wsa="http://cxf.apache.org/ws/addressing"; allowDuplicates="false" usingAddressingAdvisory="true" /> I have tweaked the above seetings a lot but I cannot make it to send a single response back to ESB . Please help :( Thanks. Gaurav -- View this message in context: http://cxf.547215.n5.nabble.com/CXF-Asynchronous-Webservices-WSA-Addressing-Problem-tp4788067p4788067.html Sent from the cxf-user mailing list archive at Nabble.com.
