db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Digulla (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-2944) Derby doesn't allow more than one instance per VM
Date Sun, 05 Aug 2007 09:46:53 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aaron Digulla closed DERBY-2944.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 10.2.2.0

My question has been answered.

> Derby doesn't allow more than one instance per VM
> -------------------------------------------------
>
>                 Key: DERBY-2944
>                 URL: https://issues.apache.org/jira/browse/DERBY-2944
>             Project: Derby
>          Issue Type: Bug
>          Components: Miscellaneous
>    Affects Versions: 10.2.2.0
>            Reporter: Aaron Digulla
>             Fix For: 10.2.2.0
>
>
> If you have an IDE or a DB tool, you cannot dynamically load/unload the embedded derby
driver.
> In Eclipse BIRT, this created the following situation: The examples use Derby 10.1. My
application uses 10.2. I can't switch between the examples and the reports in my application
without restarting Eclipse and patching the Derby plugin.
> It would be great if you could add a method which we could call to cleanup the embedded
driver so we can throw the classloader away and load another instance of Derby.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message