Probably a bit late here. However, I have been using Struts 1.0 on Jboss
2.2.2 and Tomcat 3.2.2 for a few months now and it works like a charm! I
have migrated to Jboss 2.4.1 and Tomcat 3.2.3 with no effort at all, I
simply dropped in the new servers and re-deployed my ear file.
The only thing that I found tricky was the initial setup of the build.xml
file. The app.jar file contains all EJB code. The lib/app-client.jar file
contains all the interface code. And the app.war file contains a normal
tomcat deployable war file including the full file structure and classes of
the application (minus EJB and interfaces).
So in the end, I currently have a >200 class and >100 jsp system using all
the taglibs and struts components, and I have never received a class not
foud exception that wasn't deserved.
Good luck, I hope this helps and any questions are welcome.
Later,
Jake T.
-----Original Message-----
From: bill milbratz [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 18, 2001 10:37 AM
To: [EMAIL PROTECTED]
Subject: The final word on struts and jboss 2.2.2 and tomcat 3.2.2
I'd like to confirm from the Struts Authorities, that indeed, struts
doesn't quite-work-right with tomcat 3.2.2 and jboss 2.2.2. (Classloader
problems and sundry "'class not found" exceptions). Does jboss-2.4.1a and
Tomcat-3.2.3 solve the problem?
I've seen a few posts on this topic:
This one suggests that Tomcat 3.3 makes the problem disappear:
http://www.mail-archive.com/[email protected]/msg14601.html
This one suggests a workaround which involves precompiling the jsp pages:
http://www.mail-archive.com/[email protected]/msg12335.html
This one suggests dropping back to tomcat 3.2.1
http://www.mail-archive.com/[email protected]/msg12400.html
thanks in advance,
bill m
