Given a set of services C from a composite operation consisting of or containing one or more deployment, and a set of services D from a deployment installed within the operation, the deployment is considered in error when:

1. All ACTIVE services in C are UP, or
2. have one or more missing dependency, or
3. have one or more failed dependency, or
4. are themselves in a failed state

AND one or more services in D:

1. have one or more missing dependency, or
2. have one or more failed dependency, or
3. are themselves in a failed state

Then a deployment shall be considered to be failed.

For each failed deployment, a failed message should be logged with a summary of the problem. All missing dependencies should be associated with the applicable deployment dependent(s) and listed. Services which are failed should be listed BUT not with the failure cause or stack trace, which will have appeared in the log already.

Deployments that have failed will also cause the runtime portion of the operation to be treated as failed; the deployment or server start operation handler may act on this information as it would with any failed operation.

A failed deployment may become successful later on if a missing dependency is satisfied as a result of another deployment being installed. A previously successful deployment may enter a failed state if a required, satisfied dependency is later uninstalled. At the conclusion of an operation which causes a previously successful deployment to be failed, a message need not be logged however that can be considered for this or a later release.