Thanks. In the end I wrote I equivalent bean to PropertiesComponet using PropertyPlaceholderConfigurer which both use the same shared code for obtaining properties from an external source.
The only downside is that you need to declare two property resolvers beans if you want a property to span both camel & springs contexts, plus the properties get loaded twice. Not a big deal and keeps things simple. -- View this message in context: http://camel.465427.n5.nabble.com/Using-PropertiesComponent-tp4299191p4807142.html Sent from the Camel - Users mailing list archive at Nabble.com.
