Hi Arnaud, sorry no icing here ;)
The principal way of configuration is one configuration for one service, or a couple of configuration for a couple of services of the same interface (Managed Service Factory). So there is no way of sharing configuration between services. But you can have a service which only contains shared configuration which is used by the other services as depending service. This way your dependent services are only started if the "common" service is available. regards, Achim 2015-09-25 10:04 GMT+02:00 Arnaud Deprez <[email protected]>: > Hi folks, > > I would like to have your opinion about my needs. > I've several bundles which all need their custom configuration (own PID) > but all of them depends on some common configuration depending on which > environment (ie: test, production) my karaf instance is running. > > I'm currently using apache blueprint. So I would like to do is for > example, if I use [[env.name]] it will retrieve the config value from > global configuration and if I use {{bundle.name}}. > > So my questions is : > Is there a way to use common/global configuration with my current bundle > configuration ? > If yes, is it possible with blueprint or do I have to change my tech stack > ? > What are best practices ? > And icing on the cake, do you have example ? > > Rgds, > > Arnaud > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
