Actually, this is not required by the spec. Note that this section of
the spec is talking about session beans. A session bean is what "An
instance" refers to in the first sentence. In parens "(sessions or
entities)" is referring to the "other EJB objects" it has references to.
Therefore, all that is required is that session beans be able to have
references to both entity and session beans that remain valid after a
passivation and activation cycle. With entity beans, it all depends on
the capabilities of the container and datastore.
However, I agree, it would be a nice feature for the container to do all
the work of mapping serializable objects and EJBObject references to the
datastore.
Tom Valesky wrote:
> 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?
>
--
-------------------------------------------------------------
Boris Chen ([EMAIL PROTECTED]) - Senior Software Engineer
BEA Weblogic http://weblogic.beasys.com - Phone: 415/364-4690
===========================================================================
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".
