IMHO, I think we need a clarification on this behavior from Vlada. It seems
likely that EJB vendors are going to go in different directions on this one.
The container's behavior when referenced beans are deleted or when containing
beans are deleted (cascading deletes) should be specified.
Rickard �berg wrote:
> On EJB1.1 CMP.
>
> If a Entity bean uses CMP and references another bean, the CMP
> implementation might support saving the reference in the database. What
> should happen if the bean is passivated and when it is later activated
> the referenced bean is no longer available?
>
> Should the container:
> a) set the reference to null
> b) throw some exception (i.e. the bean instance can never be loaded
> again, unless the referenced object is recreated /w same pk)
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> Homepage: http://www-und.ida.liu.se/~ricob684
>
> ===========================================================================
> 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".
--
Richard Monson-Haefel
Senior Consultant
BORN Information Services
Author of Enterprise JavaBeans
Published by O'Reilly & Associates
(Available June 1999)
===========================================================================
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".
