WildFly Exploded Deployments with CLI: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
Exploded deployments are not deployed by default by a WildFly instance. They can be triggered by [[WildFly_Exploded_Deployments_with_auto-deploy-exploded|configuring the deployment scanner]], using [[WildFly_Exploded_Deployments_with_Marker_Files|marker files]] or via CLI. The procedure to trigger the deployment with CLI is described below. | Exploded deployments are not deployed by default by a WildFly instance. They can be triggered by [[WildFly_Exploded_Deployments_with_auto-deploy-exploded|configuring the deployment scanner]], using [[WildFly_Exploded_Deployments_with_Marker_Files|marker files]] or via CLI. The procedure to trigger the deployment with CLI is described below. | ||
=Procedure= | |||
=="Explode" the JEE archive== | |||
Expand the JEE archive. The archive can be expanded in any local directory accessible to the application server, not necessarily under the <tt>deployments</tt> directory. | |||
Revision as of 23:19, 31 March 2016
Internal
Overview
Exploded deployments are not deployed by default by a WildFly instance. They can be triggered by configuring the deployment scanner, using marker files or via CLI. The procedure to trigger the deployment with CLI is described below.
Procedure
"Explode" the JEE archive
Expand the JEE archive. The archive can be expanded in any local directory accessible to the application server, not necessarily under the deployments directory.