You guys chat amongst yourselves if you like.Why does people get in to trouble when depending on ThreadContext classloader which is the correct way to load classes with (if one want to be container friendly :)
Depending on ThreadContext classloader will work if the container follows the spec - and if there are no TCL, then use class.forname - but remmeber to do it from a method/class that is loaded with your classes own classloader ....
/max
I do not like this kind of workarounds too, but some containers heve problems with this, I do not have any problems myself, but there are a lot reports from users. Possible some users have problems to configure container and workarounds will not help.
I don't want to use common logging for a _single_ (nearly-never-called) warning. That is my reason, and nothing to do with context-classloader.....
Regards,
- Paul H
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
