Laird,
Yes, in the case where the child object is not really "dependent" (i.e.
PhoneNumber it is not actually aggregated by Person) then PhoneNumber needs
to be an EB so that its life cycle is managed independently of Person.
-Chris.
> -----Original Message-----
> From: Laird Nelson [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, January 24, 2000 9:16 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Entity beans referencing other entity beans
>
> dan benanav wrote:
> > I may be misinterpreting your question because this does appear to be an
> issue
> > of fine grained versus
> > coarse grained component design. Why would you store the phone number
> as an
> > entity bean and
> > not just a regular business object? Then you could just use a vector
> of
> > PhoneNumber objects in the
> > Person object.
>
> (I have a related question, so I'll answer this from my point of view,
> not from the original poster's.)
>
> In my case, phone numbers can be shared among people. Consequently, I
> wouldn't store them as regular business objects because they are not
> wholly contained by one person. Or at least that's my thinking. Is
> that a valid counterexample?
>
> Cheers,
> Laird
>
> ==========================================================================
> =
> 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".
===========================================================================
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".
