[ https://issues.jboss.org/browse/WFCORE-4597?page=com.atlassian.jira.plugi... ] Yeray Borges reopened WFCORE-4597: ---------------------------------- The solution here was incorrect; using PhaseContext.getServiceTarget() we are changing the parent of the External Module Spec service created for the external module, making it dependent on the first deployment. Under these circumstances, if we deploy two applications and remove later the first application deployed, we will be removing the External Module Spec service, which, in turns is required for the second deployment. An example of this error is the following message: {noformat} [standalone@localhost:9990 /] deploy web-app-classpath-1.0.war [standalone@localhost:9990 /] deploy web-app-classpath-2.0.war [standalone@localhost:9990 /] undeploy web-app-classpath-1.0.war WFLYCTL0441: Operation has resulted in failed or missing services WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.module.spec.service."deployment.external./Users/ysantana/app-libs/echo-library-1-1.0.jar".main (missing) dependents: [service jboss.modu le.resolve.phase."deployment.web-app-classpath-2.0.war".main.1] service module.resolved.service."deployment.web-app-classpath-2.0.war".main (missing) dependents: [service jboss.module.service."deployment.web-app-cl asspath-2.0.war".main] WFLYCTL0448: 1 additional services are down due to their dependencies being missing or failed {noformat} We have to install the ExternalModuleSpecService out of the scope of the deployment, we can use EXTERNAL_SERVICE_TARGET deployment attachment for that purpose. -- This message was sent by Atlassian Jira (v7.12.1#712002)