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#a10196861 Sent from the open-jpa-dev mailing list archive at Nabble.com.
