Previously I have only used Jetty with JBoss so forgive any ignorance with tomcat specific issues.
One of my main problems stems from the use of FormProc in both of my applications. Each WAR has it's own formproc.xml in WEB-INF/classes, however only 1 formproc.xml is seen by both WAR's. This same behavior is seen with the 'Java2ClassLoadingCompliance' attribute enabled or disabled. Providing unique names to the configuration files solves the problem, however in JBoss-3.2.3 w/Jetty 4.2.15 I am able to run the application as expected with the 'Java2ClassLoadingCompliance' attribute disabled.
In an attempt to troubleshoot I also started playing with the 'UseJbossWebLoader' attribute in tomcat's jboss-service.xml. I did notice that if both the 'UseJbossWebLoader' and 'Java2ClassLoadingCompliance' attributes are set to false, all deployed web applications, including jmx-console and web-console, break. What, if any, is the relationship between these 2 attributs? Are they mutually exclusive?
Has anyone had any similar experiences, or possibly shed some light on what I might be doing wrong.
Thanks, -- Mike .................................. Mike Moulton [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
