I meant Java properties, NOT J2EE Env properties - as it would not
really make much sense at all - I mentioned Env as 'Environment' so
that the Derby DataSource Factory can decide of a classloader to use
(whether an existing one for this context (based on derby.system.home
and derby.system.classpath Java properties) or a new one to register -
if none (specific) registered, then the default class loader would be
used...
Yes, a prototype would be good to demonstrate this.
--francois
- Re: Support multiple Derby systems in one VM Francois Orsini
- Re: Support multiple Derby systems in one VM Jeremy Boynes
