Home → Extension Development →

Classloaders and extensions

• Edit

Kevin Stembridge

06 Jan, 2016 11:02 PM

Hi,
I've got a vague recollection of reading somewhere that extensions have their own classloader. But that doesn't seem to be the case in recent versions.

I've had a couple of issues because I package JFreeChart and HttpClient in my mxt but those jars are also shipped with Moneydance. It seems the version in Moneydance takes precedence.

I've got everything working ok by downgrading to the same versions used in Moneydance but I would prefer to use more recent versions of these libraries. I'm also concerned that there could be compatibility issues because we have differing release cycles. I would have to cater for the lowest common denominator.

Having a ClassLoader hierarchy where the extension loader takes precedence would be ideal for me. Is this how it is intended to work?

Cheers,
Kevin

1. 1 Posted by Kevin Stembridg... on 25 Mar, 2016 01:17 PM

   

   Hi,

   Does anyone have any feedback on this?

   Cheers,
   Kevin

   • Edit

2. Support Staff 2 Posted by Sean Reilly on 25 Mar, 2016 01:30 PM

   

   Hi Kevin,

   Thanks for making me feel old... I barely remember writing the classloader code about 15 years ago! If I remember correctly the system does take precedence but I'll look into whether or not that can be changed. I think my initial worry might have been that extensions could override core classes, but that should be easy enough to filter out in the loader.

   I'll have to make sure that no other issues come up, but at least at first I don't foresee any problems with it.

   Thanks,

   Sean Reilly
   Developer, The Infinite Kind
   http://infinitekind.com

   • Edit

3. 3 Posted by Kevin Stembridg... on 25 Mar, 2016 01:35 PM

   

   Hi Sean,

   You were probably just a teenage computer whiz back then so you don't have any feet in the grave yet. :)

   Thanks for looking into it.

   Kevin

   • Edit

4. System closed this discussion on 24 Jun, 2016 01:40 PM.