[
https://issues.apache.org/jira/browse/DERBY-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513363
]
Aaron Digulla commented on DERBY-2944:
--------------------------------------
How about running two versions of Derby in two classloaders in the same VM?
> 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
>
> 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.
