Re: Blueprint and property placeholder

2016-09-22 Thread Matt Pavlovich

update-strategy="none" will stop automatic reload of _all_ properties. There is 
not a way to indicate partial update, since all the beans are restarted when a 
configuration change occurs.


On 9/20/16 1:43 PM, dpravin wrote:

Hello All,

We have some common properties, not integration/bundle specific. Can
multiple routes/bundles refer to these property files from blueprint using
cm:property-placeholder?

I also found out that if you have set update-strategy="reload" the bundle
get restarted irrespective of the property being used by the bundle. Is this
the default behavior? Is there anything that can help avoid reload/restart
of bundle if the property is not used?

Thanks,
Pravin



--
View this message in context: 
http://camel.465427.n5.nabble.com/Blueprint-and-property-placeholder-tp5787763.html
Sent from the Camel - Users mailing list archive at Nabble.com.




Re: Blueprint and property placeholder

2016-09-21 Thread Brad Johnson
I don't believe the same properties can be used by multiple bundles yet.  I
think it's in the specification but isn't implemented in Aries yet.

Anyone out there that knows otherwise please correct.

On Tue, Sep 20, 2016 at 12:43 PM, dpravin  wrote:

> Hello All,
>
> We have some common properties, not integration/bundle specific. Can
> multiple routes/bundles refer to these property files from blueprint using
> cm:property-placeholder?
>
> I also found out that if you have set update-strategy="reload" the bundle
> get restarted irrespective of the property being used by the bundle. Is
> this
> the default behavior? Is there anything that can help avoid reload/restart
> of bundle if the property is not used?
>
> Thanks,
> Pravin
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.
> com/Blueprint-and-property-placeholder-tp5787763.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>