I don’t know if jbossweb-tomcat50.sar is officially supported yet but I’ll notify you of the problem I’m having anyway.
I have a .war in an .ear that uses container managed FORM security. I was originally developing in 3.2.2RC3 + jbossweb-tomcat50.sar instead of jbossweb-tomcat41.sar. Everything worked great in 3.2.2RC3. However, when I attempt to deploy my application in 3.2.2 I get the exception below. It appears to be something wrong with the logging configuration but I really have no idea what. It also appears to be localized to the new jbossweb-tomcat50.sar because if I deploy the jbossweb-tomcat50.sar from 3.2.2RC3 in 3.2.2 everything works fine. In addition if I convert my web-app to a 2.3 web-app and deploy it in 3.2.2’s jbossweb-tomcat41.sar then it deploys fine. Any ideas?
This happened earlier with TC standalone and Struts webapps. Basically, the fix for all cases is to put commons-logging in the main classpath.
However, it is very likley that TC 5 will end up using (like 4.1) a JB provided loader for the webapp repositories. This would also solve the problem.
-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxx Rémy Maucherat Senior Developer & Consultant JBoss Group (Europe) SàRL xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
