Forums Register Login

Bean Instance

+Pie Number of slices to send: Send
In Stateful Session Bean,after client finishes the job whether bean is destroyed and instance is moved to pool or instance of bean itself is destroyed.

+Pie Number of slices to send: Send
Hello Vidya,

In case of stateful session beans there is no such thing as "pool", atleast this is whats clear from the lifecycle diagram of a stateful session bean. But yes in case of a stateless session bean, there is a "pool" of instances maintained.

And so, we can conclude that once a remove() is invoked on a steteful session bean, the bean instance goes to "does not exist" state.

Regards,
Tiro.
+Pie Number of slices to send: Send
Thanks Tiro for your reply.

One more Doubt,for the same case how Entity Bean will react?
+Pie Number of slices to send: Send
Hi Vidya,

In stateful session beans, there is no interaction with the pool. In case of stateless session beans,entity beans, we have.

In both entity,state less session beans the instance couldnt be removed, will be used for some other jobs. The bean instance will go back to the pool.

But in case of Entity beans the only data from the database will be deleted not the instance.

Thanks
Srija
"Don't believe every tiny ad you see on the internet. But this one is rock solid." - George Washington
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 659 times.
Similar Threads
unsetSessionContext
EJB 2- Stateless session bean problem
Scope of t:saveState
Lifecycle of a SFSB with respect to activation
ejbRemove??
More...

All times above are in ranch (not your local) time.
The current ranch time is
Apr 16, 2024 06:23:43.