View source for WildFly Exploded Deployments with auto-deploy-exploded

=Internal=

* [[WildFly Exploded Deployments]]
* [[WildFly Deployment Scanner Subsystem|Deployment Scanner Subsystem]]

=Overview=

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

<pre>
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
</pre>

=Configuring the Deployment Scanner to Auto-Deploy Exploded Deployments=

Configure the deployment scanner setting the <tt>auto-deploy-exploded</tt> attribute to <tt>true</tt> as such:

<pre>
        <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>
</pre>

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

=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.