The long answer (or several long answers, at least one good written by Craig) can be found by searching the archives of this list.
The short answer is that it is a classloader issue. The classes in struts.jar instantiates your action classes and formbean classes. Those classes _really_ _really_ should be packaged with the webapp and stored below the WEB-INF/classes dir (or inside a jar in WEB-INF/lib if you really want to jar them). If struts.jar is in WEB-INF/lib it will find your classes and everything will be good :-). If struts.jar is somewhere else in the classpath, the classes inside your webapp will not be found by the struts.jar classes and you will see strange errors when trying to run things. Regards Mikael At 11:14 2002-03-12 -0600, you wrote: >I want to start out by saying that I have read the fine manual and realise >that the struts FAQ says that the struts.jar "must not" be placed on the >application server's CLASSPATH. > >My question to this list is why is this the case? I have a build manager >who very much wants only a single instance of any jar file to exist on a >server and they are asking why I am talking about putting multiples of the >same file on their machine? > >Simon > >----------------------------------------------------------------- >Simon P. Chappell [EMAIL PROTECTED] >Java Programming Specialist www.landsend.com >Lands' End, Inc. (608) 935-4526 > >-- >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]>
