Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <16687918.274991284822952130.JavaMail.jira@thor>
Date: Sat, 18 Sep 2010 11:15:52 -0400 (EDT)
From: "Harald Wellmann (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Created: (OPENJPA-1803) Unwrap EntityManager to Connection
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Unwrap EntityManager to Connection
----------------------------------

                 Key: OPENJPA-1803
                 URL: https://issues.apache.org/jira/browse/OPENJPA-1803
             Project: OpenJPA
          Issue Type: Improvement
          Components: jpa
    Affects Versions: 2.0.1
            Reporter: Harald Wellmann


This is currently the recommended way to access the javax.sql.Connection underlying an EntityManager:

        OpenJPAEntityManager oem = OpenJPAPersistence.cast(em);
        Connection con = (Connection) oem.getConnection();

It would be more convenient to simply write

        Connection con = em.unwrap(Connection.class);

That way, the client needing to access the Connection only depends on the javax.persistence API and not on org.apache.openjpa.*.

I believe the JPA 2.0 spec neither mandates nor forbids this functionality. It is supported by Eclipselink 2.x.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.