[ http://jira.jboss.com/jira/browse/EJBTHREE-73?page=history ] Bill Burke resolved EJBTHREE-73: --------------------------------
Resolution: Rejected EJB3 already uses a ThreadLocal for SLSBs > Unpooled SLSB semantics > ----------------------- > > Key: EJBTHREE-73 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-73 > Project: EJB 3.0 > Type: Feature Request > Versions: Preview 5, Preview 4 > Reporter: Andrew Oliver > Assignee: Bill Burke > > Original Estimate: 1 day > Remaining: 1 day > > EJB3 should allow optional servlet-style thread model semantics for stateless > session beans. Meaning, rarely is object pooling of SLSBs of any real > advantage aside from contraining resources which is usually better done in > places like thread pools and isn't commonly made use of to constrain > individual application components in practice. > basically a "@TheadSafeSLSB" or some like tag would mark that it was safe to > send all threads to the a single instance of an SLSB. You'd follow similar > practices that you use for Servlets which you almost have to do anyhow for > SLSBs. You'd no longer be granted an object lock for the scope method > invocation. > Possibly this should be the default behavior. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- 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-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development