Should work just fine, especially if you only rely on jax-ws or somesuch interface for communicating with the outside world. That is to say, if you don't work directly with the CXF innards such as the bus, the exchange and interceptors, during your concurrent execution - not that I don't think there's a good and thread-safe way to do this, I just caution to a little thinking toward getting it right.
On 4/7/08, Sica, David (David) <[EMAIL PROTECTED]> wrote: > I'm creating a web service that needs to do some processing that will > take too long to perform and return to the client synchronously. I'm > considering giving the client back a transactionid immediately, storing > it in a database, then spawning a thread which will do the long running > task and update the database mapping between the transactionid and the > results which the client can query later. > > My main question is if there's anything special I should consider about > spawning threads from a CXF web service in this fashion or if this is a > bad idea? > > Thanks, > > David > > -- Venlig hilsen / Kind regards, Christian Vest Hansen.
