If you deploy a web application which has a web fragment with a relative ordering referring to a non-existent fragment, it will fail. This was reported as JBAS-8767, Remy said the spec was not clear so he would ask, and them it was fixed for AS 6.0. The fix does not appear to have been incorporated into AS7. I am unsure as to the result of the spec clarification on whether it should work, but since it was fixed in AS6 it probably should for EAP as well.
Upstream AS 6 changeset was https://source.jboss.org/changelog/JBossAS6/?cs=110198
The same validation code seems written in class "WarMetaDataProcessor.java": https://github.com/undertow-io/undertow-subsystem/blob/master/extension/src/main/java/org/jboss/as/undertow/deployment/WarMetaDataProcessor.java "throw new IllegalStateException(MESSAGES.invalidRelativeOrderingUnknownName(webOrdering.getJar()))"
(In reply to Jason Peng from comment #3) > The same validation code seems written in class "WarMetaDataProcessor.java": > > https://github.com/undertow-io/undertow-subsystem/blob/master/extension/src/ > main/java/org/jboss/as/undertow/deployment/WarMetaDataProcessor.java > > "throw new > IllegalStateException(MESSAGES. > invalidRelativeOrderingUnknownName(webOrdering.getJar()))" Also in EAP 6.3, the validation is written in this file: org.jboss.as.web.deployment.WarMetaDataProcessor.java "throw new IllegalStateException(MESSAGES.invalidRelativeOrderingUnknownName(webOrdering.getJar()));"
Verified with EAP 6.4.0.ER2