In previous versions of JBoss EAP 6, the check for duplicate values for deployment runtime-name attributes in a server group on startup was too aggressive.  It was incorrectly throwing an error on startup if there were any duplicate runtime-names in the whole domain, instead of just in a single server group.

As a result, including multiple deployments in a domain with the same runtime-name would result in a boot failure even if those deployments are not mapped to the same server group.

For example:
----
JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
...
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1348,9]
...
Message: JBAS014664: An element of this type named 'example.war' has already been declared
----
 
In this release the validation of uniqueness of runtime names was moved from the XML parser to the operation execution logic, and the validation logic was adjusted to ignore duplicates not associated with the same server group.

Multiple deployments with the same runtime-name value can now coexist in a domain so long as they are not mapped to the same server group.