Right now the class loader used for loading extension classes does not
have a parent class loader set see
com.vividsolutions.jump.workbench.plugin.PlugInManager.
I think that it should have a parent and it be set to the class loader
of the PlugInManager class (which is the system class path).
Sounds reasonable to me.
Larry
On 9/14/07, Paul Austin [EMAIL PROTECTED] wrote:
Right now the class loader used for loading extension classes does not
have a parent class loader set see
com.vividsolutions.jump.workbench.plugin.PlugInManager.
I think that it should have a parent and it be
It's OK I found a work around, I agree if we don't have to mess with
classloaders then we shouldn't
Paul
Paul Austin wrote:
Right now the class loader used for loading extension classes does not
have a parent class loader set see
com.vividsolutions.jump.workbench.plugin.PlugInManager.
I
well .. if there would be a possibility to define a custom class loader
this would enable an extension to load its own jars circumventing
conflicts with possible existing other versions of a library used by
jump or another extension. a nice feature from my point of view.
problem is: as far as
