[
https://issues.apache.org/jira/browse/DERBY-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484516
]
Kathey Marsden commented on DERBY-1228:
---------------------------------------
I think you are correct; an alternative to derby.system.home is the main
issue. We need to provide an alternate way to specify the location for
reading the properties file. Additionally, DERBY-700 would need to be
fixed and we would need testing to make sure things like aggregates work
with two instances of Derby loaded in the same jvm.
> Make it possible to run multiple instances of Derby within the same VM
> ----------------------------------------------------------------------
>
> Key: DERBY-1228
> URL: https://issues.apache.org/jira/browse/DERBY-1228
> Project: Derby
> Issue Type: New Feature
> Components: Services
> Reporter: David Van Couvering
>
> Make it possible to run multiple instances of Derby within the same VM, each
> with its own derby.system.home, separate configuration parameters, and even
> different versions of Derby jar files. I haven't looked at this carefully,
> but at first glance I think this would require (a) refactoring Derby code to
> get all configuration from a configuration API rather than directly from
> system properties (b) write a configuration API/class that supports a
> properties file as well as system properties (in the future this class could
> also work with JMX) (c) the ability to specify the derby.system.home and a
> classpath as a DataSource property (d) a Derby classloader that loads Derby
> jar files from the classpath specified on the DataSource
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
