You essentially get the same stateless bean behaviour with java service endpoints as you get with EJB service endpoints. There is no point of contention, every client is assigned its own service endpoint instance.
The difference is the pooling behaviour. With EJB you hav precreated SLSB instances in the pool. With JSE you get a new (unpooled) instance for every request. Of course, you can have multiple concurrent requests. The number of concurrent WS requests would be limmited by the capabilities of the transport layer. e.g . if you use SOAP over HTTP you can have maxThreads="250" concurrent requests configures in tomcat View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868275#3868275 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3868275 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
