Andrew is correct. JAX-WS async is purely a convenience mechanism to allow the application avoid creating a separate thread to manage the invocation direction.
What you really need to avoid is tying up the client->server connection for the duration of the long-running invocation. This could be achieved via WS-Addressing with a decoupled response endpoint , so that the client->server may be torn down once the request has been transmitted and the response when ready is sent over a separate server->client connection. Though it sounds like WS-A is not an option for you. Otherwise you can model a polling-style (as suggested by Glen) or callback-style of interaction in the WSDL. Cheers, Eoghan 2009/8/6 Andrew Clegg <[email protected]> > 2009/8/5 conficio <[email protected]>: > > > My question is: Does the asynchronous Web service some active polling > across > > the TCP connection to keep it alive? Is that the solution I'm looking > for, > > Asynchronous invocation? > > I'm happy to be corrected if wrong, but I believe the actual TCP > conversation is basically the same for CXF sync/async service > invocation, it just *appears* to work asynchronously from the POV of > the client code. > > For really long-running jobs you are probably better off doing proper > server-side asynchronous services with persistent state, like this: > > http://www.jroller.com/gmazza/entry/creating_service_side_asynchronous_web > > Andrew. > > -- > :: http://biotext.org.uk/ :: >
