Hi,
In EJB 2.0 PFD1, the persistence implementation was allowed to
change a visible primary key of a dependent object. This was
useful in the case of a compound primary key which contains a
foreign key in a relational database. (See 9.4.5.) I guess the
roughly equivalent situation in EJB 2.0 PFD2 would be potentially
changing keys for local objects in a relationship.
In EJB 2.0 PFD2, the following passage seems to indicate that the
container is not allowed to change the primary key: "Note that the
container�s implementation of the referential integrity semantics for
container managed relationships must not cause the value of the
primary key to change." (See 10.3.5.) Although the language
("referential integrity") seems to limit itself to the "side effects" of
relationship mutators (setter methods of beans and collections), I
tend to read this as a blanket prohibition against changing the keys.
If I'm reading this correctly, I was wondering what people thought
about the implications for the above-described object/relational
mapping situation... (Also I'm interested in alternate readings of the
spec.)
===========================================================================
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".
