There has been some work on trunk (and the branches) in the last couple weeks to clarify some of the WS-Addressing one-way handling and the 202 return codes and such. Thus, this may already be fixed in the latest 2.4.3 and 2.5.0 snapshots. Any chance you can give those a try?
Dan On Friday, September 09, 2011 8:20:12 PM gauravd wrote: > Iam using Websphere Message Broker 7 as an ESB. There are multiple message > flows - one for sending calling the cxf service and second flow for handling > the response from cxf service. Its the second flow where Iam seeing the > problem. > > Can you help me out please. I am not sure if 2 responses sent by CXF, - > one with anonymous declarations and second with actual response payload is a > standard practice? > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/CXF-Asynchronous-Webservices-WSA-Addressing > -Problem-tp4788067p4788618.html Sent from the cxf-user mailing list archive > at Nabble.com. -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
