Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
Date: Thu, 15 Sep 2011 16:00:04 -0400
Message-ID: 
 <CANYnOKS3W9oRSyF=JRBUAvoD3VEupXLtiOdDjs6HNWQKXAU14A@mail.gmail.com>
Subject: JDBC operation in JPA transaction
From: Daryl Stultz <daryl.stultz@opentempo.com>
To: OpenJPA User List <users@openjpa.apache.org>
Content-Type: multipart/alternative; boundary=bcaec52e57c79ca9cf04ad00523d

--bcaec52e57c79ca9cf04ad00523d
Content-Type: text/plain; charset=ISO-8859-1

Hello,

consider the following code in an entity "save" method:

em.getTransaction().begin();
try {
// get a hold of JDBC connection so we can join transaction
OpenJPAEntityManager emo = (OpenJPAEntityManager) em;
Connection connection = (Connection) emo.getConnection();
// ... do JDBC insert
connection.executeUpdate(...);
em.merge(this);
em.getTransaction().commit();
} catch (...) {
}

The idea is to start a transaction on the EM, perform an operation in JDBC,
then commit the EM transaction. When the commit fails the JDBC operation is
successful. I expected the rollback of the transaction to rollback the
operation on the JDBC connection, too. Am I doing this right? How can I
perform a JDBC operation in a JPA transaction and have it rolled back upon
failure of commit?

Thanks.

-- 
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
http://www.opentempo.com
mailto:daryl.stultz@opentempo.com

--bcaec52e57c79ca9cf04ad00523d--