Jochen~ In the particular case that I am thinking of, that I should re-write my tests to not depend on the parent classloader. In a similar (but not identical case), there was a bug the in the custom classloader that I wrote that I was trying to work around and the correct thing was to find and fix the bug. You may wish to consider something like OSGI which was designed for this sort of versioning of classes. It might be too heavy weight for your situation though.
This could of course be my bias, as I find classloaders a bit difficult to work with in general. Matt On Thu, Apr 16, 2009 at 10:53 AM, Jochen Theodorou <blackd...@gmx.org>wrote: > > Matt Fowles schrieb: > > Jochen~ > > > > In my experience playing games with classloaders like this leads to to > > breakage. I have briefly tried what you are asking about (calling > > getParent() on a classloader) and it has worked, but I have always later > > come to the conclusion that what I want to do is error prone and I > > should find a different approach. > > and what would that be? > > bye Jochen > > -- > Jochen "blackdrag" Theodorou > The Groovy Project Tech Lead (http://groovy.codehaus.org) > http://blackdragsview.blogspot.com/ > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com To unsubscribe from this group, send email to jvm-languages+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
