WildFly Exploded Deployments with auto-deploy-exploded: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 6: | Line 6: | ||
=Overview= | =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> | |||
auto-deploy-exploded="true"/> | auto-deploy-exploded="true"/> | ||
Revision as of 22:53, 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
auto-deploy-exploded="true"/>