[jboss-jira] [JBoss JIRA] (AS7-6270) DuplicateServiceException when loading different EARs with same embedded WAR name

[Stuart Douglas (JIRA)]

     [ https://issues.jboss.org/browse/AS7-6270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas closed AS7-6270.
-------------------------------

    Resolution: Duplicate Issue


Duplicate of AS7-4150, which is fixed.
                
> DuplicateServiceException when loading different EARs with same embedded WAR name
> ---------------------------------------------------------------------------------
>
>                 Key: AS7-6270
>                 URL: https://issues.jboss.org/browse/AS7-6270
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Web
>    Affects Versions: 7.1.1.Final
>         Environment: OSX Lion
>            Reporter: Wayne Schroeder
>            Assignee: Remy Maucherat
>
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.security.jacc."web.war" is already registered
> I have three EARs, all of which have their own application.xml declaring a contained web.war file in DIFFERENT context roots.  The contents of web.war in each EAR are different, it's just our packaging standard to put all the servlets for our projects in web.war.  This particular server holds three projects that have a web tier.  Now, this can change as a work around (I can change the name of the archive), but I was under the impression, after searching, that you COULD have the same WAR name in different EARs as long as their context roots were declared to be different, which in my case, they definitely are.  It seems that the name of the archive is being used as a unique identifier when it should not.
> This looks to be an exact duplicate of issue AS7-1281, but it is claimed to be fixed in 7.1.1.Final, but it seems to remain an issue.  As a work around, I just renamed the wars in my deployments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira