You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Jan Luehe <Ja...@Sun.COM> on 2005/10/01 02:10:33 UTC
Re: Classloading regression between commons-digester-1.0 and later
versions
Simon Kitching wrote On 09/30/05 16:49,:
> It's not safe to put digester in the container path and expose this to
> components. Digester uses BeanUtils which uses lots of static variables.
> Any library that uses static variables is a very *bad* thing to place in
> a path that is shared by multiple supposedly independent components.
>
> I think that allowing a container to expose classes which are not part
> of the container specification is a really bad idea in any case:
> * http://wiki.apache.org/jakarta-commons/Logging/UndeployMemoryLeak
>
> Why do you have a need to expose digester to components rather than let
> components which want to use digester bundle it in WEB-INF/lib
> themselves?
What you suggest makes perfect sense.
Thanks!
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org