Stateful vs. stateless session bean
843833Apr 20 2003 — edited Apr 23 2003Hi,
I am following the pattern of accessing entity beans with a session bean wrapper. I am just wondering if it's more efficient to make it a stateful session bean by keeping references to the home interfaces or make it stateless and do a lookup every time the session bean is created/activated?
I suppose the number of entity beans I want to access might make a difference. If so, is there a rough number when one way becomes better than the other?
Thanks for any help in advance.
Jeff