Hi Willem, thanks a lot, it works :)
On Sat, Oct 20, 2012 at 5:59 AM, Willem jiang <willem.ji...@gmail.com> wrote: > Hi, > > camel property component supports blueprint property out of box, and you can > leverage the OSGi admin service to update the property for you. > > here is an example[1] that you may take a look. > > [1]http://fusesource.com/docs/esbent/7.0/esb_deploy_osgi/DeployCamel-OsgiConfigProps.html > -- > Willem Jiang > > Red Hat, Inc. > FuseSource is now part of Red Hat > Web: http://www.fusesource.com | http://www.redhat.com > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) > (English) > http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese) > Twitter: willemjiang > Weibo: willemjiang > > > > > > On Saturday, October 20, 2012 at 6:54 AM, Martin Stiborský wrote: > >> Hello, >> I have troubles with properties files in Camel. >> I know how to define bean with location property to my properties >> file, then I can use it in camel context with {{key.something}}. >> I'd expect that it's working in the same way also outside the camel >> context, I tried also different syntaxe - ${key.something} - but, this >> is not working. >> >> Complete example: >> >> <blueprint> >> <bean id="properties" >> class="org.apache.camel.component.properties.PropertiesComponent"> >> <property name="location" value="classpath:my.properties"/> >> </bean> >> <bean id="myBean" class="my.Bean"> >> <property name="something" value="${key.something}" /> <!-- >> not working :( --> >> </bean> >> >> <camelContext> >> </camelContext >> >> </blueprint> >> >> >> Is there a possibility to use one properties file both inside and >> outside camel context? >> >> Thanks! >> >> -- >> S pozdravem >> Martin Stiborský >> >> Jabber: st...@njs.netlab.cz (mailto:st...@njs.netlab.cz) > > -- S pozdravem Martin Stiborský Jabber: st...@njs.netlab.cz
