Skip navigation links
WildFly: Core Parent Aggregator 2.2.0.Final

Package org.jboss.as.server.deployment

The JBossAS domain deployment subsystem classes.

See: Description

Package org.jboss.as.server.deployment Description

The JBossAS domain deployment subsystem classes.

Deployment of a unit (typically an archive) has a number of distinct phases.

  1. Phase 0: Domain Controller. This phase runs on the domain controller to perform a first-pass validation of all descriptors and other meta-information in the deployment unit.
    1. Deployment Type Identification. The type of deployment is identified, so that the proper validation sequence and deployer chain can be selected.
    2. Descriptor Validation. All descriptors in the deployment are initially validated. This typically will entail a simple XSD validation, plus a limited degree of structural validation.
    3. Domain Deployment. This phase runs on the domain controller to install the validated deployment unit into the domain model itself, and coordinate the distribution of the domain update to the relevant servers, using the deployment plan to coordinate distribution appropriately.
  2. Phase 1: Server Deployment Preprocessing. This phase runs on the individual server to prepare a deployment unit for execution. After this phase, the "parent" service for the deployment item and the service corresponding to the virtual file mount are available.
    1. Deployment Type Check. If the deployment type corresponds to a subsystem that is not present in the current profile, log a message and do no further processing.
    2. Deployment Mount. Mount the deployment unit into the Virtual File System.
  3. Phase 2: Server Deployment Unit Processing. This phase runs on the individual server to process the deployment unit into actual deployment items. No service batch is active during this phase.
    1. Deployment Processing. In this phase, the chain of DeploymentUnitProcessors which is associated with the deployment unit type are executed over the deployment unit to parse any descriptors, add them to the DeploymentUnit, transform them, and/or convert them into DeploymentItems. These DeploymentItems represent the deployed state of the deployment unit.
  4. Phase 3: Installation. In this phase the deployment items are actually executed and added to a service batch, causing their corresponding services to be resolved and started up.

The deployment items corresponding to a deployment unit are started, stopped, and removed by way of a unit-wide dependency service.

Skip navigation links
WildFly: Core Parent Aggregator 2.2.0.Final

Copyright © 2023 JBoss by Red Hat. All rights reserved.