I was a bit surprised to realize that the etc/*.cfg files are all for blueprint property file configuration and don't have anything to do with config admin. I was also mildly surprised to find that config admin settings are all in the config admin data area so they are wiped out by a clean start.
I think at least some karaf services would be easier to set up and configure using DS, the metatype service, and config admin than with blueprint: the features service looked especially good for this approach. I'd like to suggest keeping the config admin data under etc/conf, possibly adding an additional clean option to clean this too, and converting at least "easy" karaf services to use config admin possibly through DS. I personally haven't gotten the aries blueprint config admin namespace handler to work, nor does it seem to me to have good semantics for property change, nor is it standardized, so I'm biased towards DS. If blueprint + config admin works and there's a good reason to use it I don't have a problem with it. thoughts? thanks david jencks
