cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: JAXWS Asynchronous consumption of webservice
Date Mon, 30 Mar 2009 18:44:19 GMT
On Mon March 30 2009 2:33:25 pm Rao, Sameer V wrote:
> Thanks Dan,
>
> So does it mean that the default WorkQueue used by the Bus is registered
> with the container's mbean server?

It is, kind of.   :-)

The workqueue isn't created until the first time it's needed.   Thus, if you 
just startup the process, it won't be there in the jmx view.   However, once a 
service that needs it accesses it, it will appear. 

Dan


>
>
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Monday, March 30, 2009 1:02 PM
> To: users@cxf.apache.org
> 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
dkulp@apache.org
http://www.dankulp.com/blog

Mime
View raw message