> [mailto:[EMAIL PROTECTED]]On Behalf Of Richard Monson-Haefel
> > >From the spec I gathered that a dependent object is
> > one whose life cycle and access is controlled by some
> > other object.
> >
>
> This is not correct. A dependent object is not necessarily owned
> by an entity bean or other dependent object. They can live
> independently and even end up completely disconnected from
> all other object.
Just to clarify the above, this is of course true when we
talk about the dependent object as defined in the EJB 2.0
spec.
In my opinion there is no clear 1-1 relationship between
the EJB 2.0 dependent object concept and UML
aggregation/composition (especially when you are used to think
of the composite part of the composition as the "dependent").
One have to take care when mapping the UML conceptual class
diagram to EJB design. The mapping rules are not cut in stone.
Regs, Bartek
--
This transmission is for the intended addressee only and is confidential
information. If you have received this transmission in error, please
delete it and notify the sender. The contents of this e-mail are the
opinion of the writer only and are not endorsed by Mincom Limited unless
expressly stated otherwise.
===========================================================================
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".
