Originally posted by rajenag neelam:
1)I want to know whether multiple cleint access is supported in Statefull Session beans.
Originally posted by rajenag neelam:
2) I read in a book that for Stateless session bean there will be pool,
and for Statefull session bean there will be cache.
And For entity bean there will be both pool and cache.
Please explain me How they are realted with Lifecycles and clients of that beans.
SCJP 1.4 / 5.0 - SCBCD 1.3 - SCWCD 1.4 - IBM 484
Originally posted by Severin St�ckli:
[B] no, see above. The main difference is that a Stateful session bean has a conversational state. This has different impacts:
- Only one client can have a conversation with the same bean instance
- multiple client calls can be made in one transaction (BMT only)
- clustering is more difficult (session synchronization)
...
Severin
SCJP 1.4 / 5.0 - SCBCD 1.3 - SCWCD 1.4 - IBM 484
Originally posted by Vinicius Boson:
The stateful session bean will not be pooled because its lifecycle dependes of the client. When the client calls create on the component interface (EJBObject or EJBLocalObject) the container calls the bean�s default contruct followed by the callback setSessionContext and ejbCreate. The bean�s states will be cached (storaged in memory) while the bean is activated. When the client calls remove on the component interface, the container will call the callbacks ejbRemove and the bean will be destroyed. PUFT !!! There�s no need for pools.
Marco Tedone<br />SCJP1.4,SCJP5,SCBCD,SCWCD
You’ll find me in my office. I’ll probably be drinking. And reading this tiny ad.
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|