As I mentioned on the ServiceMix dev list, there is a "deficiency" in the "Client" API that would make this change relatively moot unless the client API is completely updated. Right now, async invokations are only available to the jax-ws frontend, and that's really just "faked" via doing a sync invokation on a background thread (which then blocks). We would definitely need to get the Client API's updated to support async concepts a bit better before the transports can really be updated to take advantage of it.
Dan On Monday 25 August 2008 3:28:21 am Freeman Fang wrote: > Hi, > > Currently we are using sync way for jms transport which means the thread > get blocked until response messsage is coming or the client side > timeout, see the handleResponse() method of JMSConduit? Is it possible > that we use non-block way for JMSConduit, something like implement JMS > MessageListener API? Or any special reason we need this sync invocation > for JMS conduit? > > Thanks > Freeman -- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog
