-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
-
-
-
-
-
-
https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-documentation/merge_requests/3282, https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-documentation/merge_requests/3345, https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-documentation/merge_requests/3375
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1469079
Title: Control the order of Deployed Applications on JBoss EAP 6
Describe the issue: Clarification of the use of the jboss-all.xml file
Suggestions for improvement:
jboss-all.xml lets you declare dependencies that the server doesn't otherwise detect, it is not strict ordering feature, if there are missing dependencies then the deployment fails.
The jboss-all.xml assumes the dependencies have already been deployed or are available. If they are not available it does not mean EAP will automatically deploy the undeployed dependencies to satisfy the dependency.
Additional information:
Confusion around this resulted in a support case.
- clones
-
JBEAP-12022 [7.1] Configuration - Control the order of Deployed Applications clarification
- Closed