WildFly Exploded Deployments with auto-deploy-exploded: Difference between revisions
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
</pre> | </pre> | ||
=Configuring the Deployment Scanner to Auto-Deploy Exploded Deployments= | |||
Configure the deployment scanner as such: | |||
<pre> | |||
</pre> | |||
Revision as of 22:54, 31 March 2016
Internal
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 as such: