Hi Hyndavi, Well the datasource option should work for you right now.
At this time I don't have free cycles to look into providing a connection to the EntityManager. I suspect we'll find a large number of cases where OpenJPA is managing the connection for you (potentially closing it). So I've opened a JIRA issue on your behalf: https://issues.apache.org/jira/browse/OPENJPA-1772. If there's a lot of interest, or someone submits a patch we can take another look. Best Regards, On Tue, Aug 17, 2010 at 2:31 AM, hyndavi <[email protected]> wrote: > > Hi Mike, > > Thank you very much for your response. > > Yes. I have existing customized API that helps us to create Datasource and > Connection objects based on Database availablility. This also maintains > connection pools, checks Database availablility and etc. > > We are planning to use JPA going forward. With that we would like to > integrate this customized API. > > -Hyndavi. > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Integrating-existing-customized-Datasource-and-Connection-objects-in-JPA-tp5411498p5430996.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
