Thanks Dan, So does it mean that the default WorkQueue used by the Bus is registered with the container's mbean server?
-----Original Message----- From: Daniel Kulp [mailto:[email protected]] Sent: Monday, March 30, 2009 1:02 PM To: [email protected] Cc: Rao, Sameer V Subject: Re: JAXWS Asynchronous consumption of webservice On Mon March 30 2009 1:21:32 pm Rao, Sameer V wrote: > Per the JAXWS specs, a service can be consumed asynchronously > (SOAP/HTTP). In this case WSDL2Java generates the required code in > Service Interface (i.e. Future<>. > > I am not able to figure out how to configure CXF to use a specific > ThreadPool or Does CXF internally manage the ThreadPool and also > register the pool with the JEE container? I am using CXF in JBoss, and > per JEE App container standard applications should not create/spawn > threads as they are not visible to he container. Does CXF handle this > internally or should applications (consumers) need to handle ThreadPool > stuff? By default, CXF should use the WorkQueue on the Bus. We have a default one configured in for that. The Service class (that the generated serviced objects extend) has a "setExecutor" method on it that can be used to set a specific executor that is used if you don't want to use our default one. -- Daniel Kulp [email protected] http://www.dankulp.com/blog
