I would like to know the answer to the following question:
Is the use of "ON DELETE CASCADE" prohibitted with EJB
entities that map to database tables? If not, how does
the EJB container find out that other records have been
deleted from the database? On page 97, section 8.4,
Figure 20 of the EJB 1.1 spec, it says that a "direct
delete" moves EJB object from "exists and referenced" to
"does not exist and referenced". I wonder how the
EJB container handle a situation where a bean instance
is in ready state, and its equivalent record has been
deleted from the database? That is the bean has not
been passivated, and someone else deleted that record
from the database (via ON DELETE CASCADE, for instance).
===========================================================================
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".
