Agreed. I think we must provide a way to easily upgrade a component (for example) using a ant / maven task without having to undeploy all the SAs, shutting down the component, uninstall, reinstall, start, redeploy the SA.
Actually, this code is not really in the AutoDeploymentService, but in the mbeans for the components, shared libraries and service assemblies. The Registry is keeping track of pending components / sa that need to be restarted. We will also need to bypass the tests that may reject uninstalling the component if there are some SU deployed on it that are performed in InstallationService#install. I think we could add a boolean property "upgrade" on the ant tasks, which would be given to the AdminCommandsService#installComponent. In such a case, if the component is already installed, it would force an uninstallation prior to installing the component, and all SUs should be put back in the same state (i think we just need to keep the state of the component to restore it). Any better idea ? Cheers, Guillaume Nodet On 7/24/06, Philip Dodds <[EMAIL PROTECTED]> wrote:
I have been hitting problems with the Maven plugin in situations where I need to work out the dependencies and then other components outside the scope of the component being deployed are using the dependencies that this component wishes to stop. When using the hot-deploy directory ServiceMix is able to work out the dependencies and stop dependants using an re-install. I'm wondering if we should look at doing this as an extension to the ANT tasks to provide the functionality, this could then be re-used in the Maven plugin? Thoughts? P
