Hi!
"Tye, Tim" wrote:
>
> ejbRemove is called just before the instance is removed from WebLogic's
> container cache.
This is not correct. Please read questions carefully before answering.
The question was about stateful session beans, and ejbRemove() on the
bean is called immediately as a consequence of remove() being called on
the EJBObject.
Tim's reply applies to the case of stateless session beans.
/Rickard
> > In a system I am working on, I need to know when ejbRemove()
> > is actually called on stateful session beans. For example,
> > if a client calls remove(), is ejbRemove() called immediately?
> > The other is if the beans times out (I know about the passitivate
> > issues), is ejbRemove() called immediately or could it be delayed
> > at the container's option?
> >
> > I've read the EJB spec and was unable to find any material on
> > this. In
> > reality, I only care about what WebLogic does as I have
> > decided with the
> > state of the market today real portability is not possible.
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
