WildFly Exploded Deployments: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 13: Line 13:
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.
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.


If the server is not specifically configured to do exploded deployments, and if the directory has one of the standard JEE extensions (.ear, .war, etc), the application server will not deploy it. However, and this is counterintuitive, if the directory has a non standard extension or no extension at all, the application server will try to deploy it, or deploy something.


<font color=red>
=WildFly Exploded Deployments with <tt>auto-deploy-exploded</tt>=


<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[WildFly Exploded Deployments with auto-deploy-exploded|WildFly Exploded Deployments with <tt>auto-deploy-exploded</tt>]]
</blockquote>


* deployment scanner
=WildFly Exploded Deployments with Marker Files=
* marker files
* CLI


<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[WildFly Exploded Deployments with Marker Files|WildFly Exploded Deployments with Marker Files]]
</blockquote>


If the directory has one of the standard JEE extensions (.ear, .war, etc), the application server will not deploy it.
=WildFly Exploded Deployments with CLI=


If the directory has a non standard extension or no extension at all, the application server will try to deploy it.
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
 
:[[WildFly Exploded Deployments with CLI|WildFly Exploded Deployments with CLI]]
 
</blockquote>
auto-deploy-exploded="true"/>
 
 
</font>

Latest revision as of 01:14, 1 April 2016

External

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.

If the server is not specifically configured to do exploded deployments, and if the directory has one of the standard JEE extensions (.ear, .war, etc), the application server will not deploy it. However, and this is counterintuitive, if the directory has a non standard extension or no extension at all, the application server will try to deploy it, or deploy something.

WildFly Exploded Deployments with auto-deploy-exploded

WildFly Exploded Deployments with auto-deploy-exploded

WildFly Exploded Deployments with Marker Files

WildFly Exploded Deployments with Marker Files

WildFly Exploded Deployments with CLI

WildFly Exploded Deployments with CLI