[ https://issues.jboss.org/browse/WFCORE-1392?page=com.atlassian.jira.plugi... ] Tomas Hofman commented on WFCORE-1392: -------------------------------------- Currently the sequence of actions during deployment is: {code} DeploymentAddHandler: create deployment resource contentRepository.addContent(...) or contentRepository.syncContent(...) if (ENABLED attr is true): DeploymentHandlerUtil.deploy(...) complete step: contentRepository.addContentReference(...) DeploymentDeployHandler: set ENABLED attr to true DeploymentHandlerUtil.deploy(...) DeploymentHandlerUtil.deploy(): if (is normal server): emit notification add RUNTIME step: create and install deployment and content services {code} During undeployment: {code} DeploymentUndeployHandler: if (ENABLED attr is true): DeploymentHandlerUtil.undeploy(...) DeploymentHandlerUtil.undeploy(): if (is normal server): emit notification add RUNTIME step: remove deployment and content services DeploymentRemoveHandler: remove deployment resource if (is normal server): add RUNTIME step: if (ENABLED attr is true): remove deployment and content services complete step: contentRepository.removeContent(...) {code} So the asynchronicity is in that content is added into content repository in both, normal and admin-only mode, but is removed from content repository only in normal mode. The modifications would be purely in DeploymentRemoveHandler: {code} DeploymentRemoveHandler: remove deploymetn resource if (is normal server): add RUNTIME step: if (ENABLED attr is true): remove deployment and content services complete step: contentRepository.removeContent(...) + else: + add RUNTIME step: + complete step: + contentRepository.removeContent(...) {code} DeploymentRemoveHandler is used in both, standalone and domain servers. Host controller in domain mode already removes the content during undeployment in both modes, so no changes are necessary there. -- This message was sent by Atlassian JIRA (v7.5.0#75005)