Re: Using PropertiesComponent

2011-09-15 Thread jason.parr
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 bo

Re: Using PropertiesComponent

2011-09-15 Thread bvahdat
Hi Jason, see: http://camel.apache.org/how-do-i-use-spring-property-placeholder-with-camel-xml.html and the ticket Claus talked about is this one (Reporter is James Strachan): https://jira.springsource.org/browse/SPR-4466 Regards, Babak -- View this message in context: http://camel.465427.n5

Re: Using PropertiesComponent

2011-09-15 Thread jason.parr
Yes understand but it not a single properties file it's code to load a hierarchy of properties. And I can't find the post your talking about as mentioned before, I may have missed something but could you reference the post's url? >>>ie Alternatively is to use that delegate spring bean that a Came

Re: Using PropertiesComponent

2011-09-15 Thread Preben.Asmussen
year - that's a weak point. I end up using a mix of Spring and Camel properties whenever the properties file contains a dynamic reference e.g. environment variable reference. At the moment I define elements in the camel context to be able to use Spring property placeholders, but it's not the nice

Re: Using PropertiesComponent

2011-09-15 Thread Claus Ibsen
On Thu, Sep 15, 2011 at 12:27 PM, jason.parr wrote: > > We had assumed that camel's PropertiesComponent resolution would be visible > within the general Spring context and wrote our own camel PropertiesResolver > to walk a complex hierarchical tree of config. > > This all works fine with the camel

Re: Using PropertiesComponent

2011-09-15 Thread jason.parr
We had assumed that camel's PropertiesComponent resolution would be visible within the general Spring context and wrote our own camel PropertiesResolver to walk a complex hierarchical tree of config. This all works fine with the camel world but falls flat on it's face when trying to resolve stand

Re: Using PropertiesComponent

2011-04-13 Thread jpalmer1026
Hi Claus, Thanks for the explanation. That's sort of a bummer that the context:property-placeholder tag is required. Not a huge deal or anything, just not as DRY (don't repeat yourself) as it could be. You asked how I reference the property from the bean. I do that just by following normal Spring

Re: Using PropertiesComponent

2011-04-12 Thread Claus Ibsen
On Tue, Apr 12, 2011 at 11:38 PM, jpalmer1026 wrote: > Hi, > > I have a properties bean defined in my Spring application context file that > I use to specify the location of an externalized property file. The problem > I'm having is that I need to reference properties contained in the > externaliz