Hi, well putting everything in WEB-INF/lib...
If you are doing a corporate-framework and want to disable the application-people to change or override the framework you have to place all framework-components out of WEB-INF/lib... So we are back at point 1... regards Alexander -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 11:55 PM To: Struts Developers List Subject: Re: Bad classloading, why does Struts continue to use Class.forName()? On Tue, 15 Jan 2002, Colin Sampaleanu wrote: > Date: Tue, 15 Jan 2002 15:35:25 -0500 > From: Colin Sampaleanu <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > To: Struts Developers List <[EMAIL PROTECTED]> > Subject: Re: Bad classloading, > why does Struts continue to use Class.forName()? > > Thanks. The bug report mentions the Digester only, but the problem is > not only with the usage of the Digester though, it is with Struts > itself. We have a legitimate use for Struts at several levels, and the > current use of Class.forName() for classloading in a number of places > breaks things. > Of course, you are disobeying the documentation that says to put the JAR files in /WEB-INF/lib (for the specific purpose of avoiding this problem), so one could quibble that it's a feature, not a bug ... :-). Nah ... Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
