DeploymentPhaseContext provides API to support wiring up various service dependency and service value injection use cases, where dependencies must be started and injections must be available before a subsequent phase's DeploymentUnitPhaseService starts. DUP's in that phase can then rely on the services having been started and can access the injected values.

The problem with this is only a DUP can access the DeploymentPhaseContext, while it may be the OperationStepHandler that installs the DUPs that logically controls this kind of wiring. This forces the OSH to install a DUP 1 to do the wiring to allow the operation of DUP 2. Or, perhaps, the subsystem author adds the wiring logic to some unrelated DUP 1 that just happens to run before DUP 2's phase.

The proposed enhancement is to add wiring API to an interface accessible to the OSH. The interface impl would ensure that the appropriate service dependencies and injections are set up when deployment starts.

DeploymentProcessorTarget seems like a candidate interface where this kind of API could be exposed.