WildFly Exploded Deployments: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
<font color=red> | <font color=red> | ||
* deployment scanner | * deployment scanner | ||
* marker files | * marker files | ||
* CLI | * CLI | ||
If the directory has one of the standard JEE extensions (.ear, .war, etc), the application server will not deploy it. | |||
If the directory has a non standard extension or no extension at all, the application server will try to deploy it. | |||
auto-deploy-exploded="true"/> | auto-deploy-exploded="true"/> | ||
</font> | |||
Revision as of 22:30, 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
If the directory has one of the standard JEE extensions (.ear, .war, etc), the application server will not deploy it.
If the directory has a non standard extension or no extension at all, the application server will try to deploy it.
auto-deploy-exploded="true"/>