> -----Original Message----- > From: Conor MacNeill [mailto:[EMAIL PROTECTED]
> I can give you another example from JNDI - when you use the > InitialContext, > you pass it the classname of a factory object. Now since the > InitialContext > is part of the JDK, if it were to use Class.forName, you > would only be able > to find factory classes in the system classpath. This code, > however, uses > the context classloader associated with the current thread > which allows a > class in the JDK to instantiate a class not on the system > classpath. That is cool. Yes, but this is the expected behavior and perfectly logical... Here in fact what I had in mind was if there was some *trouble* (bugs/features) associated with Class.forName() use. For example I bumped into this message: http://lists.w3.org/Archives/Public/www-jigsaw/1999JanFeb/0046.html That I cannot relate to anything I know of. -- St�phane Bailliez Software Engineer, Paris - France iMediation - http://www.imediation.com Disclaimer: All the opinions expressed above are mine and not those from my company.
