[
https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40160
]
Guillaume Nodet commented on SM-1071:
-------------------------------------
Yeah, good idea to investigate. It may be a bit a complex api just to retrieve
a document, but at least it's a standard one. I've no experience with JCR so
far.
I'm not sure we need to mandate the use of this api to retrieve the
configuration. We just need to be able to:
* detect if the configuration has changed
* download it
So maybe a simple custom interface could be written, and one implementation
would delegate to JCR, another to pure HTTP or webdav, another to LDAP...
> 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.
