openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phill Moran" <pjmo...@rogers.com>
Subject RE: provide an actual JDBC connection?
Date Thu, 26 Apr 2007 13:06:03 GMT
Have you tried to use Spring? I think you may be able to get that with
dependency injection. Not positive but thought I would throw in that suggestion 

-----Original Message-----
From: tbee [mailto:tbee@tbee.org] 
Sent: April 26, 2007 5:10 AM
To: open-jpa-dev@incubator.apache.org
Subject: provide an actual JDBC connection?


Is it possible to provide an actual JDBC connection instead of connect
parameters?

The business model I'm trying to construct will work inside an existing
application which does direct JDBC. There is already a connection open and it
would be a waste of resource to have two. I can always hack together a special
Driver for this. Another solution would be to use the connection of OpenJPA.

One concern: how many actual JDBC connections are opened during a run. I assume
that only one is opened and that the JPA "transaction" concept is not directly
related to the JDBC transactions. That JDBC transactions are only used during a
JPA transaction's commit phase.
--
View this message in context:
http://www.nabble.com/provide-an-actual-JDBC-connection--tf3650466.html#a1019686
1
Sent from the open-jpa-dev mailing list archive at Nabble.com.


Mime
View raw message