Tobias Bocanegra wrote > sure. afaik, the goal is not to allow modification to the > configuration directly on the storage. like you wouldn't mess with the > properties files of the filebase config. > managing the config would still go through the normal osgi config > admin, but the store would be in the repository. this has the big > advantage, that everything your application needs, can be stored in > the repository (bundles, scripts, content, config) and can be > backed-up, replicated, clustered, etc. with repository means. so a > sysadmin does not need to backup the filesystem based config > separately. > But that's a different thing then - the jcrbundles only installs configs from the repo. If you change a config through the web console this is not reflected in the config files. If you want to use the repo as the store for the config admin, you have to implement a persistence store for the config admin. But this has nothing to do with jcrbundles then.
Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
