On Tue, Aug 21, 2012 at 5:36 PM, Marina Vatkina
<marina.vatkina_at_oracle.com>wrote:
> If we use the following text in the section 4.8.5 Singleton Session Bean
> Concurrency, it makes it a developer responsibility to make sure the
> context is thread safe, if more than one thread can access that singleton
> instance at the same time:
>
> "It is legal to store Java EE objects that do not support concurrent
> access (e.g. references to Java Persistence entity managers or stateful
> session beans) within the singleton session bean instance state. However,
> it is the responsibility of the Bean Provider to ensure such objects are
> not accessed by more than one thread at a time."
>
Right; I take it then that an EJBContext is *definitely* one of those "Java
EE objects that do[es] not support concurrent access".
(In any event, your answer is quite clear; I'll add the requisite locking.)
Best,
Laird
--
http://about.me/lairdnelson