WildFly Exploded Deployments with auto-deploy-exploded

Internal

• WildFly Exploded Deployments
• Deployment Scanner Subsystem

Overview

Exploded deployments are not deployed by default by a WildFly instance. If a directory with a standard JEE extension (.ear, .war, etc.) is encountered in the deployments directory, a standardly configured WildFly instance will issue a log message similar to:

15:51:08,008 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found test.ear in deployment directory. To trigger deployment create a file called test.ear.dodeploy

Configuring the Deployment Scanner to Auto-Deploy Exploded Deployments

Configure the deployment scanner setting the auto-deploy-exploded attribute to true as such:

        <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
            <deployment-scanner path="deployments" 
                                relative-to="jboss.server.base.dir" 
                                scan-interval="5000" 
                                auto-deploy-exploded="true"/>
        </subsystem>

Once configured, the deployment scanner will pick up and deploy exploded JEE archives.

Reliable deployment behaviour is not possible when auto-deployment of exploded content is enabled (i.e. deployment without use of ".dodeploy"' marker files). Configuration of auto-deployment of exploded content is not recommended in any situation where reliability is desired. Configuring the deployment scanner's auto-deploy-exploded setting to "false" is recommended.

Redeployment on Any File Change

A particular behavior of the deployment scanner in this configuration is that it re-deploys the artifact if detects any file change (not only on specific deployment descriptors) under the root directory of the artifact.