Hi Thomas, Thomas Dudziak wrote on Tuesday, September 06, 2005 9:09 AM:
[snip] > > * the direct usage of types (Integer.TYPE etc.) has obviously > problems in environments with multiple class loaders (eg. > Class.forName(String name, boolean initialize, ClassLoader > classLoader); likewise there may or may not be issues with > using static in this context Just out of curiosity: Why? These classes will always come from the system classloader ... > * int.class is not guaranteed to be equal to Integer.class Any reference? I am quite sure, that this will break a lot of apps (at least those who rely on DataInput/DataOutput). And you would no longer be able to serialize between different runtimes ... > * Class.forName is known to be problematic in certain > circumstances/environments; using > Thread.currentThread().getContextClassLoader() might be more > useful (as Henri/Stephen suggested). > > I'll add an issue for this in BugZilla with my code attached, > and you guys can decide whether it is useful to include in > commons-lang, ok ? > > regards, > Tom Thanks for anwering, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
