cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "EVENO Manuel" <>
Subject RE: Asynchronous Invocation and connection keep alive on the TCP level
Date Thu, 06 Aug 2009 14:39:21 GMT

Do you have example or documentation of a "decoupled response endpoint"
or the callbacks-tyle mecanism you wrote about ?
I can find anything on the CXF Wiki ...


-----Message d'origine-----
De : Eoghan Glynn [] 
Envoyé : jeudi 6 août 2009 16:04
À :
Objet : Re: Asynchronous Invocation and connection keep alive on the TCP level

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 

Otherwise you can model a polling-style (as suggested by Glen) or callback-style of interaction
in the WSDL.


2009/8/6 Andrew Clegg <>

> 2009/8/5 conficio <>:
> > 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:
> _web
> Andrew.
> --
> :: ::

View raw message