Hi Enrique,
Strange. I was almost certain that Hibernate would work that way as well. If
just leave the defaults one, the EntityManager doesn't know what to do with a
detached entity instance.
I've tried with one sample project and this is what I get with
Hibernate:org.hibernate.TransientPropertyValueException: object references an
unsaved transient instance
If I add the Cascade then it works fine.
Maybe you have Cascade set up somewhere else?
Cheers,Roberto
From: Enrique Rodríguez Lasterra <laste...@gmail.com>
To: users@openjpa.apache.org
Sent: Wednesday, August 3, 2016 5:29 AM
Subject: Migration from hibernate
Hi, i'm new on the list. I'm migrating a project from tomcat+hibernate to
websphere+openjpa2.2.3
My problem is with a @ManyToOne relationship.
I have a Customer entity with a relationship with CustomerType.
When i create a new customer i don't whant to save-update customertype.
This pseudo-code work with hibernate
Customer c = new Customer();
CustomerType ct = new CustomerType();
ct.setPk(1);
c.setCustomerType(ct);
....
entityManager.persist(c);
When i execute it with openjpa, i get an exception that CustomerType is
detached and i shoud user Cascade.Persist, but this is not what i want.
I know that one way to resolve the problema is to find CustomerType on
EntityManager instead to create a new object for that... but this change is
very complex in my application.
Is this a problem of openjpa or hibernate implementation?
--
_______________________________
Enrique Rodriguez Lasterra
lasterra AT gmail DOT com
