On 9/6/05, Thomas Dudziak <[EMAIL PROTECTED]> wrote: > On 9/6/05, Jörg Schaible <[EMAIL PROTECTED]> wrote: > > > 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 > > Are you sure they will ? What would hinder a custom classloader to > load them on its own ? >
A custom classloader not respecting the delegation model (i.e. overriding loadClass(String, boolean)) is surely out on a slipperly slope, no? --knut --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
