Suhel,
I assume we're talking about stateful session beans.  The problem being is a matter of consistency.  If you have two clients accessing the same instance of a stateful session bean, how do you handle concurrent updates?  State would become inconsistent.  Further more, why would you want to share stateful session beans between several clients any way... I'd have to quesion the intent of the design.
 
Is it perhaps that you really need to use stateless session beans that access entity beans?  The entity beans are the construct of choice to handle concurrent access to data by more than one client.  This is a fairly tried and true pattern, accessing EB's through SLSB...
 
-peter
 
 
----- Original Message -----
Sent: Saturday, January 26, 2002 2:04 PM
Subject: Re: ConCurrent Clients

Peter
thanks  for you your +ve answer ...........but whether EJB Specification make mandate for the Container Developers to implement this kind of policy , for all kinds of EJB 's' or is vendor specific provisions.............log me out.
 
 
-Suhel
----- Original Message -----
Sent: Sunday, January 27, 2002 12:15 AM
Subject: Re: ConCurrent Clients

Suhel,
Concurrent access on a stateful session bean is a no-no.  It contradicts the notion of SFSB, one bean, one client.
 
In stateless session beans, you'll instruct the container to pre-instantiate several instances that will be shared among clients, this is acceptable as the beans are stateless... it doesn't matter that they're shared.
 
Hope this helps.
 
cheers,
peter
----- Original Message -----
Sent: Saturday, January 26, 2002 1:39 PM
Subject: ConCurrent Clients

Hi
wards
 
how can I allow my EJB Instance  to get accessed by concurrent clients , is EJB specification allows Container Provider to  provide option in which same EJB instance get accessed by multiple clients, .....................what are the consequences of this scenario.............kindly Elaborate
-Suhel

Reply via email to