Hi, I found this post http://www.nabble.com/Best-practice-for-paused-operations-td18437412.html#a18437412 this post useful.
The key idea is "Although this looks asynchronous from the point of view of the client code, all this actually does is make a normal synchronous call in a background thread." - Nathan kpalania wrote: > > Hi, > I am trying to understand how asynchronous web services work and have been > playing with CXF (and its samples). However, it is still not clear to me. > I expect to use RESTful services but for purposes of understanding, I am > playing with the SOAP examples. Basically, this is what I want to > understand - > > * Say, I have a client that calls a web service (running on a difference > geographical location) passing some XML payload as input. > * The web service parses the XML message and does some additional > processing (involves DB roundtrips etc). > * At some point, when it is done, it has to call the AsyncHandler > (handleResponse() API). > > Given that the client library is ofcourse not available on the server > side, how does the server make the callback? It doesn't appear that the > callback is a webservice call (meaning, the server is not calling another > web service on the client side). How does this work? Could someone clarify > please! > -- View this message in context: http://www.nabble.com/Asynchronous-Web-Services-using-AsyncHandler-tp19520451p19520459.html Sent from the cxf-user mailing list archive at Nabble.com.
