Re: Session Bean

[Juan Pablo Lorandi]

Title: Message

Java Addicted questions go into alt.junkies.* newsgroup.   When you call remove(), the object goes into the "does not exist and referenced" state, a.k.a. pooled state. Hence, whichever resource you allocate in the Session Bean class constructor is still allocated.   HTH,     Juan Pablo Lorandi Chief Software Architect Code Foundry Ltd. [EMAIL PROTECTED] Barberstown, Straffan, Co. Kildare, Ireland. Tel: +353-1-6012050  Fax: +353-1-6012051 Mobile: +353-86-2157900 www.codefoundry.com -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]] On Behalf Of JavaSoft Sent: Friday, April 19, 2002 12:08 PM To: [EMAIL PROTECTED] 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