You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Albert Lee (Closed) (JIRA)" <ji...@apache.org> on 2012/02/02 17:56:51 UTC
[jira] [Closed] (OPENJPA-1803) Unwrap EntityManager to Connection
[ https://issues.apache.org/jira/browse/OPENJPA-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee closed OPENJPA-1803.
-------------------------------
Close issue in preparation for 2.2.0 release.
> 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
> Fix For: 2.2.0
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira