Removing EJB Business Delegate 2004-02-26 - By Harkness, David
Back
ashraf galal wrote:
> But I have one more comment. because I think you speak about entity
> bean not session.
I think James was spot on with his description. Stateless session beans
are managed by the container and not tied to a client. Though reading
the latest edition of Core J2EE Design Patterns you'd never know it. As
I just picked up this book, hoping it might have something new to chew
on, here's an excerpt from page 46:
"A session bean is dedicated to a single client or user."
Unless I never actually understood session beans in the first place,
this is not entirely correct. STATEFUL SBs certainly are dedicated to a
single client, but SLSBs can be used by many clients serially (one at a
time). True, during a single method invocation the bean is tied to a
client, but not for its lifetime.
"A session bean lives only for the duration of the client's
session."
Again no. SLSBs are pooled by the container and tied to a client only
during the method call. When a single client terminates its session, it
should have no effect on SLSBs.
So to the original question, with a SLSB delegate, calling remove() is
unnecessary but not harmful. For SFSB delegates, you most definitely
should call remove() at the appropriate time. That's my understanding
anyway, but I didn't write the EJB spec. ;)
David Harkness
Sr. Software Engineer
Sony Pictures Digital Networks
(310) 482-4756
===================================================================Companion
Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
