Hi Chris, AFAIK, the embedded derby is limited to a single connection. If you want to use multiple connections like this, then you'll have to move to the client/server derby. It's almost as simple to setup. You just need a different driver. Maybe you have already figured this out since you have posted to other forums as well...
Kevin On Tue, Jul 21, 2009 at 1:33 PM, Christopher Giblin <c...@zurich.ibm.com>wrote: > > Hi, > I have just completed the first steps with OpenJPA running in my Eclipse > RCP app. I use Derby with the EmbeddedDriver. So far so good. > > I have another set of plugins, Eclipse Data Tools Project (DTP), which > provide some DB management tools. However, both OpenJPA and DTP want to own > the Derby instance. When one has it, the other can not connect which is > actually to be expected. When I close the EntityManagerFactory, it frees > the db. But of course, I want to create that factory just once. > > I realize this is also a Derby question and equally a DTP question (I will > ask there, too). > > Has anyone had to reconcile this before such that both could the embedded > Derby? > > Thanks, chris > > > >
