I updated the docs to reflect his and the FAQ of resue of SLSBs from the pool
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4094495#4094495
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4094495
Thanks Pete
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4094795#4094795
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4094795
___
jboss-user mailing list
1: Maybe the documentation is a bit unclear there. If you access stateless
components concurrently, the container will supply enough instances from the
pool so that each thread will get its own instance.
To put this another way: From a threads perspective the connection between a
component
1) It doesn't mean anything to access a SLSB to be accessed concurrently - an
SLSB holds no state outside of the method you are calling. Yes, you can have
fields, but they might have data from previous uses of the bean, or none.
View the original post :
matt.drees wrote : Thanks for answering!
|
| So, now I have two questions.
|
| 1.
| Is Seam's reference documentation incorrect when it says The EJB container
allows stateless components to be accessed concurrently, and throws an
exception if multiple threads access a stateful
matt.drees wrote : Thanks for answering!
| 2.
| Does Seam similarly ensure that application-scope pojos are not
multi-threaded?
The Seam reference manual, section Concurrency model in chapter 3: The
conceptual component model contains information about it.
From what I understand based
Thanks for all of your responses (especially wschwendt; I appreciate your
detail).
I understand why injection is safe for stateless components now. I'm not
convinced injection is safe for ([EMAIL PROTECTED]) application-scope
components; when I get some free time I'll test it out and report
anonymous wrote : But it also mentions that stateless beans can be accessed
concurrently. So, what prevents the injected variables from being overwritten
by injection from another concurrent thread?
The EJB container ensures this. Session Beans are NOT multithreaded, neither
stateless session
Thanks for answering!
So, now I have two questions.
1.
Is Seam's reference documentation incorrect when it says The EJB container
allows stateless components to be accessed concurrently, and throws an
exception if multiple threads access a stateful session bean? It's hard for
me to see how
