> How does the EJB container handle a situation where
> a particular table has the ON DELETE CASCADE referential
> integrity constraint. That is when a parent record (entity
> bean) is removed on the container side, that record along
> with all it children record are deleted on the DB side.
>
>
[Chip Wilson]
The use of a cascade delete rule is a strong indication that the
parent and child objects have the same lifetime, which is almost always
composition in UML terms. A composite should not be implemented as multiple
entity beans, but as a single entity. In EJB terms, the composed object(s),
represented by the child record(s), are called dependant objects, and there
are explicit statements in the 1.1 draft discouraging the implementation of
dependant objects as separate entity beans.
===========================================================================
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".
