Package org.jboss.as.server.deployment
package org.jboss.as.server.deployment
The JBossAS domain deployment subsystem classes.
Deployment of a unit (typically an archive) has a number of distinct phases.
- 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.
- Deployment Type Identification. The type of deployment is identified, so that the proper validation sequence and deployer chain can be selected.
- 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.
- 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.
- 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.
- 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.
- Deployment Mount. Mount the deployment unit into the Virtual File System.
- 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.
- 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 theDeploymentUnit, transform them, and/or convert them intoDeploymentItems. TheseDeploymentItems represent the deployed state of the deployment unit.
- Deployment Processing. In this phase, the chain of
- 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.
-
ClassDescriptionAbstract service responsible for managing the life-cycle of a
DeploymentUnit.Base class for operation handlers that can handle the upload of deployment content.An entity which can contain attachments.Represents a phase dependency that gets attached to the phase context or the deployment unit.An immutable, type-safe object attachment key.AListmeant for use with anAttachableobject.Service in charge with cleaning left over contents from the content repository.Deployment unit processor that adds content overrides to the VFS filesystem for overlays that could not be initially resolved.Deprecated, for removal: This API element is subject to removal in a future version.To be removed without replacement.Service wrapper forDeployerChains.Handles addition of a deployment to the model.Handles deployment into the runtime.A general/parent exception for all deployment related exceptions.Handler for the "explode" operation that can be performed against zipped managed content.Handles replacement in the runtime of one deployment by another.Utility methods used by operation handlers involved with deployment.Handles listing module dependencies of a deployment and sub-deployment.Deprecated, for removal: This API element is subject to removal in a future version.Provides VFS mounts of deployment content.Deployment unit processor that adds content overrides to the VFS filesystem.The deployment unit processor context.Handles redeployment in the runtime.Handles removal of a deployment from the model.Handles replacement in the runtime of one deployment by another.Support for creation of resources on deployments or retrieving the model of a resource on deployments.Handles undeployment from the runtime.The deployment unit.An exception which is thrown when deployment unit processing fails.A deployment processor.Handler for the upload-deployment-bytes operation.Handler for the upload-deployment-stream operation.Handler for the upload-deployment-url operation.Helper class with static methods related to deployment TODO: this should probably be somewhere elseMarks aDeploymentUnitas an EJB deployment.Handler for the "add-content" operation over an exploded managed deployment.Marker that can be used to determine if a deployment is an exploded deployment or notHandler for the "remove-content" operation over an exploded managed deployment.JPA Deployment markerHandler for the "browse-content" operation over an exploded managed deployment.Handler for the "read-content" operation over an exploded managed deployment.Manifest helper methodsContentReference built from the Management Model.An enumeration of the phases of a deployment unit's processing cycle.Marker for sub deployments that are not globally accessible, such as war's.A processor which creates a service loader index.An attachment holding the names of services detected in the deployment unit.An action that sets up and tears down some form of context (e.g. the TCCL, JNDI context etc).A simple implementation ofAttachablewhich may be used as a base class or on a standalone basis.Marker for sub deploymentsDeployment processor responsible to creating deployment unit services for sub-deployment.Marker for sub deployments which will be mounted exploded