Right, using ConfigAdmin is the way to go in OSGi. If you use blueprint for example, you just have to define a specific proprty placeholder and it's really easy to use.
On Thursday, December 9, 2010, Freeman Fang <freeman.f...@gmail.com> wrote: > Hi, > You can put properties in $KARAF_HOME/etc folder and reference it from all > bundles using ConfigAdmin service. > Freeman > On 2010-12-9, at 上午7:41, Mike Van wrote: > > All, > > The application we are building has several properties files used by all of > our bundles. Some of these properties files are .xml, some are plain old > .properties files. Currently, I am including them in each bundle, something > which makes thier maintenance quite a pain. We would like them available to > all bundles, and to have them stored in a single place. > > So far I have tried placing them in packages which contain code, but the > compiler only picks up the .class files. I've also tried to create a > package underneath resources named "myApp.configurations". This is picked > up, but because it isn't exported, it is unavailable for wiring. > > How does one make a single properties file available to all bundles deployed > in Karaf? > > v/r, > > Mike Van > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Placing-properties-files-in-the-classpath-tp2054553p2054553.html > Sent from the Karaf - User mailing list archive at Nabble.com. > > > -- Freeman Fang > ------------------------ > FuseSource: http://fusesource.comblog: > http://freemanfang.blogspot.comtwitter: http://twitter.com/freemanfangApache > Servicemix:http://servicemix.apache.orgApache Cxf: > http://cxf.apache.orgApache Karaf: http://karaf.apache.orgApache Felix: > http://felix.apache.org > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
