As Grzegorz pointed out you have to have the reload flag in to hot swap values. And it's important that you make sure you specify the 1.1.0 of cm in your header as the reload doesn't work earlier.
Having said that, if you change the value in the .cfg file and then start you Fuse instance it should preferentially use the .cfg values. Is that much happening? Also, when you look at the Header to make sure the reload works. http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0 http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.1.0.xsd";> //May be obvious but make sure the .cfg is not part of the PID. Otherwise if the PID below were foo.bar.cfg it would be looking in the etc directory for a file called foo.bar.cfg.cfg. <cm:property-placeholder persistent-id="foo.bar" update-strategy="reload"> <cm:default-properties> <cm:property name="some" value="value" /> </cm:default-properties> </cm:property-placeholder> On Wed, Sep 14, 2016 at 6:28 AM, Grzegorz Grzybek <gr.grzy...@gmail.com> wrote: > Hello > > Did you use update-strategy="reload" in <cm:property-placeholder>? > See technical explanation here: > http://ggrzybek.blogspot.com/2015/12/camel-blueprint-test-support.html > > regards > Grzegorz Grzybek > > 2016-09-14 11:47 GMT+02:00 owain <owain@integration.technology>: > > > Hi, > > > > In Fuse it looks as though if you have a property set in xml in > > cm:property-placeholder then you cannot override it in persistent.id.cfg > > file in /etc. I could see the properties in there but they appeared not > to > > be used by the route, it just used the ones set in the xml. > > > > Is this true, if so I couldn't see it documented anywhere? > > > > O. > > > > > > > > -- > > View this message in context: http://camel.465427.n5.nabble. > > com/Fuse-Blueprint-properties-override-tp5787541.html > > Sent from the Camel - Users mailing list archive at Nabble.com. > > >
