]
Richard Opalka resolved JBAS-8871.
----------------------------------
Resolution: Done
This was fixed with Bailey's pull.
AS7 undeployment doesn't work properly for identically named
deployments (with different content)
-------------------------------------------------------------------------------------------------
Key: JBAS-8871
URL:
https://issues.jboss.org/browse/JBAS-8871
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: 7.0.0.Alpha2
Currently DeploymentUndeployHandler.undeploy() calls
controller.setMode(ServiceController.Mode.NEVER)
to "undeploy DU". This causes the following issue:
There's TestA that deploys & undeploys example.war
There's TestB that deploys & undeploys example.war too (but with different
content).
The problem is TestB will see TestA example.war content :(
This is because there's still controller (for example.war DU) registered with MSC
registry,
and it's started again during the deploy phase. The code that will start it again is
---
final ServiceController<?> controller =
serviceRegistry.getService(deploymentUnitServiceName);
if(controller != null) {
controller.setMode(ServiceController.Mode.ACTIVE);
} else {
---
located in DeploymentHandlerUtil.deploy().
The solution to this problem is to call
controller.setMode(ServiceController.Mode.REMOVE) to undeploy DU properly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: