Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of curtisr7@gmail.com designates
 209.85.214.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPyf0geCnPq0FrZT=4=xLDTGwf1KTKkf9uX4O0U61m4umT7ZRw@mail.gmail.com>
References: 
 <CAPyf0geCnPq0FrZT=4=xLDTGwf1KTKkf9uX4O0U61m4umT7ZRw@mail.gmail.com>
Date: Mon, 8 Apr 2013 12:39:32 -0500
Message-ID: 
 <CAP=qHCt8o8YB_b8YOUAfvDw6X51uftNHKF2_b+xT9ZxbY1miPQ@mail.gmail.com>
Subject: Re: Insert new record + update child object
From: Rick Curtis <curtisr7@gmail.com>
To: users <users@openjpa.apache.org>
Content-Type: multipart/alternative; boundary=047d7b41cdaa6e651304d9dcebcb

--047d7b41cdaa6e651304d9dcebcb
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It looks like your problem is that the Exam is new, yet the Person is
existing and the existing Entity gets ignored when cascading the persist
operation. I believe this is working as expected.

As long as your relationships are set to CascadeType.ALL, you could always
change your em.persist(exam); to em.merge(exam);. That would take care of
persisting the new exam, and it would also cascade the merge call to the
person.

Thanks,
Rick


On Mon, Apr 8, 2013 at 11:44 AM, Jos=E9 Luis Cetina <maxtorzito@gmail.com>w=
rote:

> Hi. I have a problem with insert and updating a reference in the same
> entity.
>
> Im trying to insert a new object (Exam) that has a reference to another
> object (Person) and at the same time i want to update an attribute
> (birthDate) of the Person object. The update never happens although i
> set CascadeType to ALL.  The only way this works is doing a persist and
> after that a merge operation.  Is this normal? Do i have to change
> something??
>
> I dont like the idea of a "manual update" using merge in the Person objec=
t
> because i don't know how many objects (child object of Exam) the user wan=
t
> to update.
>
> Entities:
>
> public class Exam{
>    @ManyToOne(cascade=3D CascadeType.ALL)
>    @JoinColumn(name =3D "person_id")
>    public Person person;
> ......
> }
>
> public class Person{
>     private Date birthDate;
>    @OneToMany(mappedBy =3D "person")
>     private List<Exam> exams
> .......
> }
>
> public class SomeClass{
>    public void someMethod(){
>       exam =3D new Exam()
>       person.setBirthDate(new Date());
>       exam.setPerson(person);
>       someEJB.saveExam(exam);
>    }
> }
>
> public class someEJB(){
>
>    public void saveExam(Exam exam){
>         ejbContext.getUserTransaction().begin();
>         em.persist(exam);
>         //THIS WORKS
>         em.merge(exam.getPerson());
>         ejbContext.getUserTransaction().commit();
>    }
>
> }
>
> Do i have to use the MERGE method for every child object?
>
>
> Here is the same question from other user:
>
> http://stackoverflow.com/questions/11029260/jpa-with-jta-persist-entity-a=
nd-merge-cascaded-child-entities
>


--=20
*Rick Curtis*

--047d7b41cdaa6e651304d9dcebcb--