Jus for info, I've solved my transport-dependant requirement by using spring-ws :
The spring-ws template is used to send synchronously the SOAP request with the expected ws-addressing replyTo. On HTTP 202, The template returns void, so I get notified the request has been accepted. I then just have to configure an EndPoint to receive the response, and extract the payload. For both operation, I reuse the JAXB marshalling code generated by CXF plugin. Nicolas. 2008/8/20 Jacques Talbot <[EMAIL PROTECTED]> > > > "Eoghan Glynn-2" wrote > >> Adrian Corcoran wrote: > >> Does CXF offer support option #2? via wsa for all supported transport? > > Its supported for HTTP. > > So, to make the link with another thread: is my understanding below > correct? > > contrarily to axis2 where you have to specify a wireasync boolean to > convince the toolkit to implement option #2, > CXF infers from the fact that WSA:ReplyTo is non anonymous that the > programmer actually wants asynchronous-on-the wire and behaves accordingly, > namely routing the http 202 ACK synchronously and the Reply-To SOAP message > asynchronously > > Correct? If yes, this is smarter! > -- > View this message in context: > http://www.nabble.com/asynchronous-call-with-ws-addressing-tp19045672p19065654.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
