Hi Bertrand My config appears in status-configurations and is also available in the component's 'activate' method whenever they change. So this part is working fine. I observed that within my sling instance, there is a config folder which had the '<service-pid>.config' file created for this service. I deleted that file and restarted sling and now the service is getting configured correctly as per the config node in the repository. Also I see that this config file is now updated correctly whenever I edit the service configuration . I think whenever a install/<service-pid>.config node gets created in the repo, the changes done to the sling:OsgiConfig node stop taking effect.
Thanks On Mon, Feb 2, 2015 at 6:24 PM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > Hi, > > On Mon, Feb 2, 2015 at 1:48 PM, connuser1 connuser1 <connus...@gmail.com> > wrote: > > ...Editing the > > config once using felix console does some (binding...?) magic which I am > > not sure of.... > > If you are able to edit your config from the Felix console it means > that it was indeed created... > > If you create sling:OsgiConfig nodes and the corresponding config > appears at /system/console/status-Configurations, all is good as far > as the installer is concerned. If your OSGi component doesn't get the > config that's a different story, probably a problem in your component. > > -Bertrand >
