WildFly Exploded Deployments: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 40: Line 40:


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

Revision as of 22:45, 31 March 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.



  • deployment scanner
  • marker files
  • CLI


If the directory has one of the standard JEE extensions (.ear, .war, etc), the application server will not deploy it.

If the directory has a non standard extension or no extension at all, the application server will try to deploy it.


auto-deploy-exploded="true"/>


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