Hello, I have a client and a server, both based on the example "ws_addressing" from CXF. I am using the decoupled mode (ie with the option DecoupledEndpoint in the client.xml). It works! I would like to make my client more reliable because the following scenario does not seem to work:
-- I start the client, it makes an asynchronous call and starts the DecoupledEndpoint for asynchronous response (Request1) -- The server sends an HTTP 202 Accepted -- Unfortunately the client's computer reboots -- Then I restart the client, it replays the asynchronous call and restarts the DecoupledEndpoint (Request2) -- When the server returns the response to the Request1, it appears that the client is unable to correlate the message. Based on this result, I have a few questions: -- Is it possible to start the DecoupledEndpoint without making asynchronous call? This would avoid the Request2 -- Is it possible to start several DecoupledEndpoint and assign to each a messageID ? -- Is it possible to persist and restore a context? This would allow my client to correlate old messages -- More generally, is there a way to support the above scenario with CXF ? Cheers, Hyacinthe Meniet -- View this message in context: http://www.nabble.com/How-to-persist-and-restore-a-cxf-client-context-tp19368970p19368970.html Sent from the cxf-user mailing list archive at Nabble.com.
