Hi, Yes, using system property is one solution, to use system property in blueprint file, you need use blueprint-ext but not blueprint-cm(blueprint-cm is for ConfigAdmin properties)
something like: <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"; xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";> <ext:property-placeholder /> <bean id="myBean" class="com.company.MyClass"> <argument value="${com.company.myProperty} /> </bean> </blueprint> And you can use both blueprint-ext and blueprint-cm together. Freeman －－－－－－－－－－－－－ Freeman Fang FuseSource Email:[email protected] Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: http://weibo.com/u/1473905042 On 2012-9-4, at 上午2:55, Christian Müller wrote: > If you use ServiceMix or Karaf, you can put your custom properties into > "etc/custom.properties" and use these placeholders in your bundle > properties file. > Than you have a central place for common/shared configuration data. > > Best, > Christian > > On Mon, Sep 3, 2012 at 2:05 PM, AlanFoster <[email protected]> wrote: > >> @Freeman-2 >> >> Hm, this isn't good to hear :( >> >> Do you happen to know of any alternatives for this? I wish to share common >> configuration across bundles with blueprint somehow >> >> Alan >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/Accessing-osgi-blueprint-property-placeholder-across-multiple-bundles-tp5718494p5718544.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> > > > > --
