>Getting the handle and storing it as a attribute would be the "normal"
>way. As you note however, this can be quite expensive. Smart containers
>should be able to manage the EJBObject instead: whenever the beans needs
>to be ejbStore:d the container should check if it's an EJBObject, if so
>it should get the Handle and store it, thus saving you the trouble of
>converting back and forth. Vendors: anyone doing this?
Actually, I think that it was Richard Monson-Haefel (sp?) who pointed
out that they _have_ to, according to section 6.4.1 of the spec.
"An instance may hold EJB object references to other EJB objects (sessions
or entities).
When the container passivates the instance after ejbPassivate, it must store
the EJB ob-ject
references with the passivated instance, and reconstruct these object
references
when it loads the instance�s state before ejbActivate."
Go figure. Did anyone actually implement this?
===========================================================================
Tom Valesky -- [EMAIL PROTECTED]
http://www.patriot.net/users/tvalesky
===========================================================================
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".
