Hi Gregory, You're conflating asynchrony with decoupled addressing.
JAX-WS asynch helps you to build asynchrony into the application (see the jaxws_async demo). This avoids tieing up an application-level thread for the duration of the invocation. WS-Addressing allows the response to be sent back over a separate server->client connection. This avoid tieing up a transport-level connection for the duration of the invocation. There are orthogonal concerns. JAX-WS async and/or WS-A can be used together or separately depending on what you want to achieve. There isn't a demo showing both together, but it shouldn't be hard for you to munge the two separate demos. Cheers, Eoghan 2009/6/25 gregory.lebonniec <[email protected]>: > > Hello, > > I have two questions concerning WS-Addressing and Asynchrony : > > 1. Concerning the CXF WS-Addressing example, I don't understand the purpose > of WS-Addressing in this case because when the client calls the service, it > is blocked (no callback method). So why send the response on another port if > the thread blocks on call ? > 2. What I am looking for is to developp an asynchronous WS-Addressing > process with callback handling. In CXF, I have found async processes but the > mecanisms are "native" to CXF and the previous example is not dealing with > asynchrony. Is there a sample which mixes asynchronous process with > WS-Addressing ? > > Thank you > > Regards, > > Greg > -- > View this message in context: > http://www.nabble.com/WS-Addressing-and-Asynchronous-processes-tp24200929p24200929.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
