It seems there were some more people struggling with the DeploymentManger interface,
i'll would like to suggest some changes i was planning to do to make it a bit easier
to use:
The current way to use DeploymentManager is (pseudo code):
| DeploymentProgress distribute = getDeploymentManager().distribute(name,
getManagedURL(name), copyContent);
| distribute.run();
|
| if (copyContent)
| {
| DeploymentProgress start = getDeploymentManager().start(name);
| start.run();
| }
|
| DeploymentProgress stop = getDeploymentManager().stop(names);
| stop.run();
|
| if (copyContent)
| {
| DeploymentProgress undeploy = getDeploymentManager().undeploy(names);
| undeploy.run();
| }
|
Well atm there is still the DeploymentPhase which should also go away.
But this looks a bit confusing.
I think it should have be symmetric whether you do copyContent or not and always have:
| deploymentManager.distribute(name, isCopyContent);
| deploymentManager.start(name);
| deploymentManager.stop(name);
| deploymentManager.remove(name);
|
So for isCopyContent == false - we should have a own transient deployment profile - which
gets activated / deactivated by the DeploymentManager.
So a isCopyContent == false app will only get removed from the repository, and not deleted
(different for isCopyContent == true).
Especially if you look at the profileService tests in the testsuite, there are a lot of
warnings from ManagementView
that the application (which are deployed with isCopyContent == false) don't exist
anymore (because there were undeployed in the testcase before)
That's because they just can get stopped, but not be removed from the repository.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205882#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...