The struts-blank.war is great and all but by default the 1.2.9 comments out
the use of any form-beans so it wouldn't be able to match your scenario at
all because your problem is right on the form bean creation. That is why I
suggested the struts-examples.war in this case.  Also, I'm talking about all
of the .jar files.  In the case of the struts-examples.war the full list of
mandatory jars would be:

antlr.jar
commons-beanutils.jar
commons-digester.jar
commons-fileupload.jar
commons-logging.jar
commons-validator.jar
jakarta-oro.jar
struts.jar

Do you have any other jars in WEB-INF/lib that we should know about?  Is all
of your custom code in WEB-INF/classes/code and absolutely not in their own
.jar file?  Also, if you do a find/search for your LoginForm class from your
main /WEBAPP directory will the word "LoginForm" only be found in
/WEB-INF/classes/code? I know you wrote it is in there but I want to be sure
there is no extra jar create by your packaging process and no extra copies
deployed somewhere by your packaging process since you mentioned your
deployment is an "exploded module".  Is that exploded module a .war or .ear
file?  I've only dealt with .war files, not .ear files.

Are there any .jar files left over in Tomcat's $CATALINA_HOME/shared/lib
directory which might shed some light on this?  Mine is always empty since I
keep a copy of all required jars in individual webapps.

Regards,
David

-----Original Message-----
From: Tom Jerry [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 09, 2006 3:14 AM
To: Struts Users Mailing List
Subject: Re: bean exception when using weblogic and NOT tomcat

all .jar files are in WEB-INF/lib folder and NOT in classes folder.
A copy of struts.jar and servlet-api jar are placed in lib folder
and from there, they are added to the build path. So there is no
problem regarding shared copy and this webapp has its own copy
of that jar. JRE System Library jdk1.4.2 is used. struts-blank.war
works. but then .... ????


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

Reply via email to