[
https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40217
]
Marcel Offermans commented on SM-1071:
--------------------------------------
One OSGi standard that I would recommend here is the Deployment Admin
specification. That used to be part of the mobile spec, but is now included in
R4.1. Deployment Admin specifies how to install a set of bundles as an atomic
operation. It also allows you to deploy artifacts other than bundles in an
extensible way (for example to include configuration information). Within the
next week or so, an implementation of that will be donated to Apache Felix, so
that might be worth looking at too.
> Provisioning system
> -------------------
>
> Key: SM-1071
> URL: https://issues.apache.org/activemq/browse/SM-1071
> Project: ServiceMix
> Issue Type: New Feature
> Reporter: Guillaume Nodet
> 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.
