Class.forName should almost never be used in a framework as this requires the class loader which loaded the class making the forName call to be able to load the requested class. This is too restrictive for a dynamic framework like JBoss.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Michael Bartmann" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 15, 2002 6:55 PM Subject: [JBoss-dev] When to use Class.forName() ?? (possible bug in JMSProviderLoader) > Hi, > for obscure reasons I find the meaning of life by integrating a MDB > together with a JMS-Provider-MBean into one ear. > It works fine UNLESS I enable ear-scoping, which is essential for me. > There is a CNFE in the JMSProviderLoader from JBoss, which uses > Class.forName(). I changed this to Thread.current...blabla...loadClass() > and it runs fine now. > But I am a bit reluctant to check this into CVS, cause I dont know the > implications for the > JBossMQ provider (I am not using that thing). > > To take it even further: > > Is there any good reason to use Class.forName() anywhere in a "normal" > MBean??? > > Enjoy, > Michael > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
