servicemix.home is the root of the servicemix installation. servicemix.base is the servicemix process's working directory, generally the same as servicemix.home if you always start servicemix from the root of your servicemix install with "./bin/servicemix". Unfortunately servicemix doesn't have the same concept as the "Sonic file system". Thanks to apache felix though there's an implementation of the Configuration Admin running that you could use, though I'm not certain this is what you're looking for - http://felix.apache.org/site/apache-felix-configuration-admin-service.html
Thanks for the information, the Admin Service looks interesting. However, if I have configuration files for Spring, XSD, ... is there a "Best Practice" location for these files in ServiceMix? Is there some type of standard deployment directory layout?
Here is what I am thinking:
Each bundle can do a:
String myConfigDirectory = BundleContext.getProperty(servicemix.base)/my_app_config
Then all my bundles can looking in to the same directory "my_app_config" for their config files. Also, when I upgrade to a new version of FUSE or move to a new machine I just have to copy over the my_app_config directory to the new installation.
Is there a better way?