DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21292>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21292 struts-config.xml interferences among wars contained in ear (in JBoss) Summary: struts-config.xml interferences among wars contained in ear (in JBoss) Product: Struts Version: 1.1RC2 Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Controller AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] It seems that struts uses static 'class' data somewhere to hold the configuration. That leads to situation that diffrent configs interfere when they are shared in ear. I have observed it in the following environment using jboss 3.2.1: I have a.ear containing b.war and c.war. Those two war's are back- and front- end based on the same framework of components. Since those components are mostly the same, they are shared at a.ear level, and each WAR uses MANIFEST.MF/Class-Path to point to them. However this leads to the situation that due to the nature of JBoss classloader both WAR's physically share the same classes. And probably becouse of this, the two applications apparently have their struts-config.xml merged. Of course, one could argue if sharing classes among web applications is politically correct and aligned with the specs. Let's not... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
