So, it means that the file is already in the etc folder at startup.
If your blueprint bundle starts after configadmin, I would consider as a fair enhancement on Aries blueprint-cm. AFAIR, blueprint-cm loads the default properties as soon as the blueprint container starts and after get the update from configadmin. Maybe it makes sense to add a property on blueprint-cm property-placeholder to check if persistent-id exists first and load it, and fallback to default properties.
Thought ? Regards JB On 10/13/2014 03:59 PM, jkraushaar wrote:
Hi JB, we create a custom distribution. The custom distribution already contains the config file in the etc folder, so it is not provisioned using features. Is there a difference between these two solutions? Regards Jochen -- View this message in context: http://karaf.922171.n3.nabble.com/Mandatory-Configuration-from-configAdmin-tp4031442p4035864.html Sent from the Karaf - User mailing list archive at Nabble.com.
-- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
