using EclipseLink as JPA 2.0 provider, I can obtain a JDBC connection by simply calling
Connection con = entityManager.unwrap(Connection.class);
But I'm unsure what I'm responsible for. Do I have to close the connection after submitting my queries? Or are I'm not allowed to close the connection, because EclipseLink also uses this connection internally. Or does it not care, because EclipseLink observes my behaviour and closes the connection automatically if I don't do it?
preguntado el 29 de julio de 12 a las 17:07
If you are in the context of a JPA transaction the connection will be managed by the provider (EclipseLink). If you are outside of a transaction you are responsible for managing the connection yourself.
See the following link for additional information:
But I'm unsure what I'm responsible for. Do I have to close the connection after submitting my queries? Or are I'm not allowed to close the connection, because EclipseLink also uses this connection internally.
A good and valid question. It seems that the documentation is lacking the semantics of the
Regarding EclipseLink, according from what I got from the fuente:
EclipseLink gives you a referencia to the currently active
connection which it uses for the currently active client session transaction. If no transaction is active, a new will be created, associated with the session and returned from the
As a result, IMHO, a commit/rollback of such a obtained
Connection may lead to undefined behavior and/or exceptions. Same is true for executing DML which changed records have been previously cached by eclipselink internal caches or for which managed entities exist.
So when using this API, especially if the underlying transaction is dirty, ten cuidado.
If you can refer to internal eclipselink classes, you can access eclipselink internal connection pool to get a
Connection exclusively (have a look at