[ https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10784: ----------------------------------------- [~manovotn] Here's an example of subsystem installing a CLEANUP deployment processor: https://github.com/wildfly/wildfly/blob/master/batch-jberet/src/main/java... The analogous class in Weld: https://github.com/wildfly/wildfly/blob/master/weld/subsystem/src/main/ja... Each Phase runs in a separate MSC service that depends on the service for the previous Phase and therefore doesn't run until all active services in that previous phase are in a rest state. So anything you do in CLEANUP will happen after all the stuff done in INSTALL is done. https://github.com/wildfly/wildfly/pull/10795 changed the Phase.INSTALL WeldDeploymentProcessor to have it add a service that depended upon others: https://github.com/wildfly/wildfly/pull/10795/files#diff-5437e2864026abc7... The same thing could be done by a Phase.CLEANUP processor, but instead of having WeldStartCompletionService depend on a bunch of other services, the fact that it's installed in CLEANUP means it runs after all those others are done. So those dependencies are not needed There may be other slightly more elegant ways to call endInitialization in CLEANUP but this seems like a simple one that changes the least amount of code. -- This message was sent by Atlassian JIRA (v7.5.0#75005)