WildFly Exploded Deployments: Difference between revisions
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
=Overview= | =Overview= | ||
Exploded deployments are not deployed by default by a WildFly instance. Special configuration or operations need to be performed in order to trigger the deployment. This article explains various methods to trigger an exploded deployment. | |||
<font color=red> | <font color=red> | ||
Revision as of 22:22, 31 March 2016
External
- How to deploy exploded applications automatically in EAP6? https://access.redhat.com/solutions/165463
- Exploded deployment not working as expected in EAP 6 https://access.redhat.com/solutions/170313
- Is it possible to do exploded deployments on EAP 6 in domain mode? https://access.redhat.com/solutions/332133
Internal
Overview
Exploded deployments are not deployed by default by a WildFly instance. Special configuration or operations need to be performed in order to trigger the deployment. This article explains various methods to trigger an exploded deployment.
- deployment scanner
- marker files
- CLI
auto-deploy-exploded="true"/>