<snip>
> 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.



>
>
> >
> >
> > >
> > > Can I have some opinions here, or should I just dive in, make a change
> > > and wait for the flak?
> > >
> > > Regards,
> > >
> > > - Paul
> > >
> > > > Folks,
> > > >
> > > > In Attributes.java, there is a single use of commons logging :
> > > >
> > > >   public static AttributeFinder getAttributeFinder() {
> > > >     ....
> > > >     } catch (Exception e) {
> > > >       logger.warn("failed to initialize specified implementation " +
> > > >       "of AttributeFinder, using default", e);
> > > >     }
> > > >     ....
> > > >   }
> > > >
> > > > Is there a chance that we could eliminate this use given that the
> > > > system recovers with the instantiation of a default AttributeFinder
?
> > > >
> > > > It would be really useful :-)
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to