I think you can have more separated with comma, eg
<propertyPlaceholder id="properties" location="blueprint:com.zotix.provider.config,blueprint:somethingElse,blueprint:blabla" />
Thank you the input. Tested the above suggestion and doesn't seem to work. Does the 'blueprint:somethingElse" need to be packed within the bundle? The idea is that to have an external property file named: somethingElse.cfg which will be attached to the container profile via git. We aim to define in somethingElse.cfg all the shared properties. Do we need to have a shared bundle with dummy blueprint and having all the shared properties defined in "properties.xml"?
Profiles inherit (overlay) so if you want common .properties / .cfg then store that in a parent profile that all your containers extend.
When using fabric then all is stored in the profiles. You have to think like that, and not think about that a file must be copied to the etc directory of karaf etc.
I understand what you mean. I have stored the shared resources properties in the parent profile but when I deploy the bundle - see extract of blueprint xml, I get an error: No component with id 'shared.resources.config' could be found.
<!-- explicitly set properties locations in blueprint -->
<propertyPlaceholder id="properties" location="blueprint:bundle-1.config,blueprint:shared.resources.config" />
The error is telling the truth as the is no component referencing that property file or pid. I can try the classpath but the whole idea is to move shared properties into a file which can be shared by all the bundles. If I remove the reference of the second shared resource property file, the bundle get installed successfully but any changes made to the shared resource property file which is attached to the parent file is not replicated in the bundle,simply because it's not referencing a second source for the properties.
There is a documentation here which shows how to source properties from two sources but to work both sources need to be available within the bundlehttp://fusesource.com/docs/router/2.8/eip/BasicPrinciples-PropPlaceholders.html#BasicPrinciples-PropPlaceholders-Blueprint
I understand the idea of attaching PID (which corresponds to the persistence-id of the properties.xml file defining the default value) to be able to override the default values the PID must somehow be referenced in the bundle. How are we going to refetene the PID which defines the shared properties? Apologies if I am repeating the same question.
Just to benefit all. Fabric support property resolver through profile - Property Resolver | Fabric8 Documentation . Using profile property resolver doesn't require explicit references of the PID in the blueprint.xml.