There should be no difference as far as documented behavior goes, but the first apparently caches classes based on equality of class loaders and can break redeployments.
-- xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
Brian Wallis wrote:
On Thu, 16 Oct 2003 08:31, Adrian Brock wrote:
While we're on the subject, somebody should explain to the jdk developers why Class.forName() has no notion of application context when there are multiple applications running on different threads in the same VM.
I'm not sure I understand the difference between:
Class.forName(name, false, Thread.getContextClassLoader()).newInstance()
and
Thread.getContextClassLoader().loadClass(name).newInstance()
But for my delegating factory only the second one works.
Thanks all for the previous replies, I have my Preferences stuff running now and think I understand a little more about how the class loading works.
brian wallis...
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
