Thanks for answering.
I looked at the code you pointed and there are things I do not understand:
How is this route deployed ? Are the properties files included in the deployment ? As part of a bundle (jar) ?
From what I know :
<cm:property-placeholder id="myConfig" persistent-id="io.fabric8.examples.camel.twitter"/>
looks for the properties file in the /etc directory of the container in which it is deployed.
Is there a fallback that looks somewhere else when not found in /etc ?
Lastly, the other 2 properties files are referenced where ?
The example is using fabric and therefore its all stored in the profile.
Points to a .properties file in the profile.
There is no files in the etc directory.
Sorry for my newbeeness but how do I store a file in the profile ?
I suppose that the file is referenced in the profile config but is has to be stored somewhere?
This file changes with each new version of the bundle so my goal would be to include it in the bundle (or feature) that I deploy.
Is it possible to do that ?
Yes a profile is just a set of files really. And profiles can be versioned, so you can create a new version and change the files in the new version.
You can add files to your profiles using the web console or from the shell in fuse. There is a profile-edit command.
Though if your project is a maven project then you can add your files to a profile by having the files in the src/main/fabric8 directory.
And then you can deploy your code to fabric, using the mvn fabric8:deploy goal
Just to be sure. Does it all apply to Fuse 6.1 GA (the version we are using) ?