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 2008/01/21 15:15:37 UTC
[jira] Moved: (SMX4KNL-11) Provisioning system
[ https://issues.apache.org/activemq/browse/SMX4KNL-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet moved SM-1071 to SMX4KNL-11:
--------------------------------------------
Fix Version/s: (was: 4.0)
Key: SMX4KNL-11 (was: SM-1071)
Project: ServiceMix Kernel (was: ServiceMix)
> Provisioning system
> -------------------
>
> Key: SMX4KNL-11
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-11
> Project: ServiceMix Kernel
> Issue Type: New Feature
> Reporter: Guillaume Nodet
> Assignee: Bruce Snyder
>
> Maybe using OBR (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or
> Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning).
> Basically, i'm thinking about two things:
> * leverage OBR to install features easily (activemq, ode, cxf, etc...)
> * dynamic / automatic provisioning of applications
> For the second one, a service could pull an HTTP url from time to time to check is a new configuration for itself is available. if yes, download it and uninstall stop / uninstall unneeded bundes, install new ones, etc...
> The configuration would be a simple xml defining which bundles / version should be started
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.