Message5480

Author leosoto
Recipients cgroves, doublep, leosoto
Date 2010-02-01.15:55:22
SpamBayes Score 0.0013681891
Marked as misclassified No
Message-id <1265039722.84.0.976007854999.issue1216@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, the devil is on the details.

The best resource I have found is <http://www.javaworld.com/javaworld/javaqa/2003-06/01-qa-0606-load.htm>. On page 3 it tells the sad truth: If the current classloader and the context classloader aren't on a (direct or indirect) parent-child relationship, there is no way to be safe. 

Whichever you pick may end up causing problems (i.e., not finding classes). And trying both (what Jython is doing now to support this feature request) may end up causing another kind of problems (basically, loading classes twice).
History
Date User Action Args
2010-02-01 15:55:22leosotosetmessageid: <1265039722.84.0.976007854999.issue1216@psf.upfronthosting.co.za>
2010-02-01 15:55:22leosotosetrecipients: + leosoto, cgroves, doublep
2010-02-01 15:55:22leosotolinkissue1216 messages
2010-02-01 15:55:22leosotocreate