[
https://issues.apache.org/jira/browse/CAMEL-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998761#comment-12998761
]
Guillaume Nodet commented on CAMEL-3704:
----------------------------------------
I agree the configuration updates should be controlled, but it just means that
the developer should be able to control what will happen at runtime, we don't
need to *force* multiple phases for bringing the configuration live. It's like
hot-deploy, some people may want the simplicity, some people may want more
control, we should allow both imho.
> Allow endpoints to receive updates from OSGi config admin at runtime
> --------------------------------------------------------------------
>
> Key: CAMEL-3704
> URL: https://issues.apache.org/jira/browse/CAMEL-3704
> Project: Camel
> Issue Type: New Feature
> Reporter: Jonathan Anstey
> Fix For: Future
>
>
> It would be neat to take advantage of the ability of the OSGi config admin to
> receive updates to an endpoint's properties at runtime and let Camel handle
> restarting the underlying services. For instance, you could have a server URL
> defined as a property
> {code}
> <osgix:cm-properties id="cmProps" persistent-id="some.config.id">
> <prop key="myServerUri">http://myserver:8888</prop>
> </osgix:cm-properties>
> <ctx:property-placeholder properties-ref="cmProps" />
> ... ${myServerUri} is used in a Camel endpoint URI somewhere...
> {code}
> In Karaf then you could change the myServerUri to something else and Camel
> would get the config update (by way of
> http://www.osgi.org/javadoc/r4v42/org/osgi/service/cm/ManagedService.html)
> and restart things as appropriate.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
