Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Date: Tue, 21 Jun 2011 14:19:47 +0000 (UTC)
From: "Rick Curtis (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Message-ID: 
 <1369759940.24500.1308665987509.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (OPENJPA-1803) Unwrap EntityManager to Connection
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENJPA-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Curtis reassigned OPENJPA-1803:
------------------------------------

    Assignee: Rick Curtis

> Unwrap EntityManager to Connection
> ----------------------------------
>
>                 Key: OPENJPA-1803
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1803
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: competitive, jpa
>    Affects Versions: 2.0.1
>            Reporter: Harald Wellmann
>            Assignee: Rick Curtis
>         Attachments: OPENJPA-1803.patch
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira