|
Hi,
I dont know from where you have read. But to be
brief , the lifecycle of the stateless bean is not controlled by the client. Its
upto container to decide to remove the instances from the pool or add to it
depending upon the load.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Cheers
----- Original Message -----
Sent: Friday, April 19, 2002 4:38
PM
Subject: Session Bean
Hi all
I have read about stateless session and stateful session, stateless means
the session object can be used by diffrent user if the object session is
free... ( this is mean the session object isnt destroyed
after a client used it but sits in the
session pool )
My question is how about if the ejbRemove() method invoked by
container, is the session object still exist in the pool ? if not, and if
i make every client that uses the session Object calls
statelessSession.remove() after finished use the session, it means the session
object will be destroyed .. so the stateless feature is gone .. am i right
?
===
thx,
a Java Addicted
|
