camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Anstey (JIRA)" <>
Subject [jira] [Closed] (CAMEL-3704) Allow endpoints to receive updates from OSGi config admin at runtime
Date Fri, 06 Jul 2012 11:53:33 GMT


Jonathan Anstey closed CAMEL-3704.

    Resolution: Won't Fix

Yeah, I agree after reading this again. I think I just thought it would be a cool feature
at the time - useful perhaps more for demos that in real life :) It is a tricky thing to impl
as you say and as well other projects (i.e. the container) handle lifecycle of bundles quite
nicely already.

> Allow endpoints to receive updates from OSGi config admin at runtime
> --------------------------------------------------------------------
>                 Key: CAMEL-3704
>                 URL:
>             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="">
>       <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
and restart things as appropriate.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message