Will -
I'm betting that the em.persist(..) call isn't happening inside a
transaction. Can you enable openjpa trace[1] and rerun your scenario?
[1] property name=openjpa.Log value=DefaultLevel=trace /
Thanks,
Rick
On Wed, May 2, 2012 at 1:12 PM, Will Hoover java.whoo...@gmail.com wrote:
I
Hi Rick,
You are correct. It isn't happening inside a transaction.
-Original Message-
From: Rick Curtis [mailto:curti...@gmail.com]
Sent: Tuesday, May 08, 2012 9:18 AM
To: users@openjpa.apache.org
Subject: Re: OpenJPA 2.2.0 + Atomikos + Embedded Jetty
Will -
I'm betting
[mailto:curti...@gmail.com]
Sent: Tuesday, May 08, 2012 9:18 AM
To: users@openjpa.apache.org
Subject: Re: OpenJPA 2.2.0 + Atomikos + Embedded Jetty
Will -
I'm betting that the em.persist(..) call isn't happening inside a
transaction. Can you enable openjpa trace[1] and rerun your scenario?
[1
(AFIK, OpenEJB doesn't support nested transactions).
Thanks for your help Rick!
-Original Message-
From: Rick Curtis [mailto:curti...@gmail.com]
Sent: Tuesday, May 08, 2012 12:25 PM
To: users@openjpa.apache.org
Subject: Re: OpenJPA 2.2.0 + Atomikos + Embedded Jetty
You are correct
I have successfully setup an OpenJPA (2.2.0) + Atomikos (3.7.1) + Embedded
Jetty (8.1.2) stack (example code below). Everything seems to works without
any errors, but OpenJPA doesn't seem to recognize dirty entities after a
call to EntityManager#persist and a new EntityManager is created (see