You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2006/03/28 23:50:35 UTC
[jira] Resolved: (SM-152) Improve behavior on install, deploy,
uninstall, undeploy
[ https://issues.apache.org/activemq/browse/SM-152?page=all ]
Guillaume Nodet resolved SM-152:
--------------------------------
Resolution: Fixed
Assign To: Guillaume Nodet
Fix Version: 3.0-M1
Hot uninstallation of a component undeploys the service assemblies and mark them as pending
> Improve behavior on install, deploy, uninstall, undeploy
> --------------------------------------------------------
>
> Key: SM-152
> URL: https://issues.apache.org/activemq/browse/SM-152
> Project: ServiceMix
> Type: Improvement
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: 3.0-M1
>
>
> 1°/ There may be some cases where a directory can not be deleted immediately. In these cases, ServiceMix should mark this directory as to be deleted, and delete it some times later (on next start ?)
> 2°/ If a component / SU is hot deployed, a file should be written with the success / error messages.
> 3°/ Shoul hot undeployment be supported ? The problem is that the deployments are linked : you can not undeploy a component before having undeployed all SU on it. Maybe SM should only handle deployment and move the deployed components / suin another dir with the result message from 1°.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira