Sorry for the late reply. No I did not find a solution to this. I did a workaround by defining both a spring property loader and a camel properties component pointing to the same file location, something which anyways had to be done before the bridgepropertyplaceholder was introduced.
-- View this message in context: http://camel.465427.n5.nabble.com/BridgePropertyPlaceholderConfigurer-properties-not-getting-resolved-tp5731172p5733590.html Sent from the Camel - Users mailing list archive at Nabble.com.
