users@jpa-spec.java.net

[jpa-spec users] [jsr338-experts] Merging of referenced new objects w/o cascade-merge specification?

From: Christian von Kutzleben <cvkutzleben_at_versant.com>
Date: Mon, 10 Dec 2012 13:56:24 +0100

Dear group,

What is supposed to happen in this scenario:

@Entity
class Person {
    //...
    Address address; //cascade-merge or cascade-all are not specified
}

@Entity
class Address {
//...
}

em.getTransaction().begin();
Person p = new Person();
em.persist(p);
em.getTransaction().commit();

em.getTransaction().begin();
em.detach(p);
p.setAddress(new Address());
Person m_p = em.merge(p);

//what does m_p's "address" field contain? Or should merge throw an
exception right away?


Thank you!

Christian

-- 
Christian von Kutzleben
Chief Engineer | Versant GmbH
(T) +49 40 60990-0
(F) +49 40 60990-113
(E) cvkutzleben_at_versant.com <cromberg_at_versant.com>
www.versant.com | www.db4o.com
-- 
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.