[
https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40241
]
Guillaume Nodet commented on SM-1071:
-------------------------------------
I've had a look at the Deployment Admin. I think it could be used instead of
OBR for installing packages, but it does not offer the feature of detecting
changes and accessing the whole configuration, so we will still need a simple
interface / implementations for that (http, jcr, jndi)...
I really see one downside to this Deployment Admin which is the fact that a
single bundle can not be shared, so I suppose that you need to install several
times the same bundle and rename it :-(
> Provisioning system
> -------------------
>
> Key: SM-1071
> URL: https://issues.apache.org/activemq/browse/SM-1071
> Project: ServiceMix
> Issue Type: New Feature
> Reporter: Guillaume Nodet
> Assignee: Bruce Snyder
> Fix For: 4.0
>
>
> 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.
