Dear group,
While reading through our Versant JPA internal state diagram (which
contains refinements of the states and transitions as needed by
our implementation), I noticed that we still had a minor question open:
The javadoc for EntityManager.detach() says:
... Unflushed changes made
* to the entity if any (including removal of the entity),
* will not be synchronized to the database. ...
Section 3.2.6 says:
...
If X is a managed entity, the detach operation causes it to become
detached. The detach operation
is cascaded...
...
If X is a removed entity, the detach operation is cascaded to entities ...
Based on the javadoc comment, I presume, that the last part should read as:
If X is a removed entity, the detach operation causes it to become
detached. The detach operation is cascaded
to entities ...
Unless this was not the intended semantics, I suggest to reword that
sentence for more clarity.
Thank you!
Christian
--
Christian Romberg
Chief Engineer | Versant GmbH
(T) +49 40 60990-0
(F) +49 40 60990-113
(E) cromberg_at_versant.com
www.versant.com<http://www.google.com/url?q=http%3A%2F%2Fwww.versant.com%2F&sa=D&sntz=1&usg=AFrqEzeeEBc_gN_8mxtt8xDB0tjXDXQVlw>|
www.db4o.com<http://www.google.com/url?q=http%3A%2F%2Fwww.db4o.com%2F&sa=D&sntz=1&usg=AFrqEzdo3Q40RwKQPBtnPIuBYQd1diFxJQ>
--
Versant
GmbH is incorporated in Germany. Company registration number: HRB
54723, Amtsgericht Hamburg. Registered Office: Halenreie 42, 22359
Hamburg, Germany. Geschäftsführer: Bernhard Wöbker, Volker John
CONFIDENTIALITY
NOTICE: This e-mail message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential or
proprietary information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient,
immediately contact the sender by reply e-mail and destroy all copies of
the original message.