| Sharing embedded Derby with other plugins [message #57407] |
Tue, 21 July 2009 17:43  |
Eclipse User |
|
|
|
Hi,
I am using OpenJPA, DTP and Derby in my Eclipse RCP app. Before I added
OpenJPA, I was using my own JDBC layer and obtained the JDBC connection
from DTP profile manager.
Now, when I use OepnJPA, I cannot connect to the database in the DSE and
navigate the tables, schemas, etc. Instead, I must stop the OpenJPA
processing, then I can connect to DSE. While DSE is connected, OpenJPA
cannot access the Derby instance.
Ideally, I could use OpenJPA and DSE simultaenously (ie, two
connections) without going Derby Client/Server. I currently use the
Derby embedded driver.
Is there a way two components such as these can access the same Derby
instance? I understand that only one can "boot" Derby.
Has anyone else come across this situation already?
Thanks,
chris
|
|
|
| Re: Sharing embedded Derby with other plugins [message #57432 is a reply to message #57407] |
Thu, 23 July 2009 10:24  |
| Eclipse User |
|
|
|
Chris Giblin wrote:
> Ideally, I could use OpenJPA and DSE simultaenously (ie, two
> connections) without going Derby Client/Server. I currently use the
> Derby embedded driver.
>
> Is there a way two components such as these can access the same Derby
> instance? I understand that only one can "boot" Derby.
>
> Has anyone else come across this situation already?
Hi Chris...
One possible solution... Create two different driver definitions for the
Derby driver so each has its own classloader (ultimately this is the
limiting factor from what I remember). See if using one for OpenJPA and
one for the DSE makes a difference.
--Fitz
|
|
|
| Re: Sharing embedded Derby with other plugins [message #596115 is a reply to message #57407] |
Thu, 23 July 2009 10:24 |
| Eclipse User |
|
|
|
Chris Giblin wrote:
> Ideally, I could use OpenJPA and DSE simultaenously (ie, two
> connections) without going Derby Client/Server. I currently use the
> Derby embedded driver.
>
> Is there a way two components such as these can access the same Derby
> instance? I understand that only one can "boot" Derby.
>
> Has anyone else come across this situation already?
Hi Chris...
One possible solution... Create two different driver definitions for the
Derby driver so each has its own classloader (ultimately this is the
limiting factor from what I remember). See if using one for OpenJPA and
one for the DSE makes a difference.
--Fitz
|
|
|
Powered by
FUDForum. Page generated in 0.37180 seconds
Home