openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey" <plins...@bea.com>
Subject RE: provide an actual JDBC connection?
Date Thu, 26 Apr 2007 16:08:19 GMT
You can't provide a JDBC connection directly, but you can provide a
DataSource, which, in turn, can provide a connection.

-Patrick

-- 
Patrick Linskey
BEA Systems, Inc.
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it. 

> -----Original Message-----
> From: tbee [mailto:tbee@tbee.org] 
> Sent: Thursday, April 26, 2007 2: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--tf365
0466.html#a10196861
> Sent from the open-jpa-dev mailing list archive at Nabble.com.
> 
> 

Notice:  This email message, together with any attachments, may contain information  of  BEA
Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,
 copyrighted  and/or legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient, and have received
this message in error, please immediately return this by email and then delete it.

Mime
View raw message