[jira] Resolved: (WW-2675) Multiple Struts2 .war in a single .ear

["Don Brown (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/struts/browse/WW-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Don Brown resolved WW-2675.
---------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 2.1.3)

Unfortunately, there is nothing we can do, other than document the case in our FAQ: http://cwiki.apache.org/confluence/display/WW/Multiple+Struts+2+wars+in+a+single+ear

If the context classloader allows Struts to see multiple instances of struts-default.xml, then the Struts is incompatible with that classloader configuration.  Even if we fixed it as a special case for struts-default.xml, you'd have all sorts of unexpected conflicts down the road with other configuration files.  Therefore, there is nothing Struts can do to fix the situation, so I've documented that this configuration may not work in our docs.

> Multiple Struts2 .war in a single .ear
> --------------------------------------
>
>                 Key: WW-2675
>                 URL: https://issues.apache.org/struts/browse/WW-2675
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Build Management, Core Actions
>    Affects Versions: 2.0.11.1
>         Environment: Glassfish v2, Eclipse
>            Reporter: Hugo de Paix de Coeur
>            Assignee: Don Brown
>
> This is a reopen of the issue https://issues.apache.org/struts/browse/WW-2668
> I've had exactly the same problem and asked on the user mailing list without solution for now : "Multiple Struts2 WAR in a single EAR" :
> http://mail-archives.apache.org/mod_mbox/struts-user/200806.mbox/%3c20080612093905.GA25760@smtp.kabhal.org%3e
> It seems the XmlConfigurationProvider of xwork does not support parsing struts-default.xml several times (1 for each .war) in a single ear.
> To reproduce the bug : just put struts2-blank and struts2-mailreader example apps in an .ear and deploy it in Glassfish

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.