Re: [jira] Updated: (DERBY-289) Enable code sharing between Derby client and engine

[Francois Orsini]

I think having 2 embedded Derby or 2 client derby apps at different version levels in the same JVM is wrong. It is technically feasible but is it rational? Separate classloaders should be used if one intends to run 2 different versions of embedded derby in the same JVM. Actually, of one of the embedded application requires a particular version of Derby, this last one better be first in the classpath - if the second one does not have a strict requirement on the version of Derby to run, then having 2 different 2 different derby.jar in the classpath is pointless...I thought we had discussed that different classloaders should be used if 2 different versions of embedded Derby (or Derby client) should run in the same JVM...