rn SINGLETON;
}
}
--
View this message in context:
http://www.nabble.com/mutithread-issues-in-interceptors-and-endpoints-tp15611836p15707562.html
Sent from the cxf-user mailing list archive at Nabble.com.
Daniel Kulp wrote:
In CXF there is a single instance of any endpoint bean that manages
all the incoming requests, or somehow there is way to have a pool of
endpoints?
With a little bit of code, yes. You can can configure in your own
invoker that does something diffent. If you look in
org.
On Friday 22 February 2008, Davide Gesino wrote:
> >> In CXF there is a single instance of any endpoint bean that
> >> manages all the incoming requests, or somehow there is way to have
> >> a pool of endpoints?
> >
> > With a little bit of code, yes. You can can configure in your own
> > invoker
ess them injecting the Web ServiceContext in the endpoint) ??
something similar to:
public boolean handleMessage(SOAPMessageContext ctx) {
ctx.put("KEY","VALUE");
...
--
View this message in context:
http://www.nabble.com/mutithread-issues-in-interceptors-and-endpoints-tp15611836p15633391.html
Sent from the cxf-user mailing list archive at Nabble.com.
On Thursday 21 February 2008, Davide Gesino wrote:
> a question about multithread issues in CXF (maybe a silly one).
> Multiple requests are managed relying upon the servlet engine I CXF
> uses. Every request (so every SOAPMessageContext) lives in his own
> thread? If there is a pool of them, every
consider?
--
View this message in context:
http://www.nabble.com/mutithread-issues-in-interceptors-and-endpoints-tp15611836p15611836.html
Sent from the cxf-user mailing list archive at Nabble.com.
