The fact that you're drawing silence on this list and Metro's list may
indicate you're thinking of this problem differently from most others. I've
been on both lists off-and-on for a few years and you're the only one I've
seen so far bringing up this issue.
A web service provider, like a web application, is really just a servlet
sitting in a servlet container. Are not your synchronicity issues better
handled at the servlet container level, just as it would for a web
application? You have a servlet (whatever CXF or Metro uses
behind-the-scenes) and you want to know how best to have it handle 1,000's
of accesses--this sounds like something best handled on the Tomcat user's
list.
All I think that you're asking is, for a service implementation bean method,
such as this:
public int doSomething(int inValue) {
return 10 * inValue;
}
is how to launch a new thread within this SIB method to do my processing of
doSomething() on a separate thread? I do not know the consequences of doing
your multithreading this way but wonder if it would be actually better to
start thinking "how do I get the servlet container to clone (or provide
enough threads for) the servlet activating this SIB so it can efficiently
handle all the requests I am expecting for it?
Stated another way, I suspect the reason why your question is not occurring
too often on the CXF and Metro lists is that most people in your situation
think in terms of the servlet container rather than the web service call for
its effective solution.
Glen
Leo Romanoff wrote:
>
> Any information about the subject?
>
--
View this message in context:
http://old.nabble.com/Server-side-asynchrony-for-SOAP-web-services-in-CXF-tp28280821p28302371.html
Sent from the cxf-user mailing list archive at Nabble.com.
