It is the same: If I click "Delete" the component configuration is removed completely and not recreated until I deliberately change something about the configuration in the repository (which leads to the EventListener being triggered). Konrad
> On 21 Jul 2016, at 08:51, Carsten Ziegeler <[email protected]> wrote: > >> Hi, >> sometimes it happens that OSGi configurations being installed through the >> OSGi Installer are manually overwritten in the Felix Web Console. >> From that point on the overwritten configuration takes precedence over the >> configuration provided through the OSGi Installer (e.g. through the JCR >> Installer Provider), therefore the latter is no longer effective. >> >> Reverting the configuration to the version being provided by the OSGi >> installer is simple for configurations not bound to a factory: You simply >> click on "Delete" in /system/console/configMgr and the OSGi Installer will >> automatically restore the configuration with the highest priority. For >> component factories it is different though. Once those are modified >> manually, there is no easy way back to the original version being provided >> from the OSGi installer. If you click on "Unbind" the whole component >> configuration is removed (and not being restored automatically). >> > What happens if you click delete for the factory configuration? > > Carsten > >> Is this just an oversight from my side or is there really no simple solution >> to fall back to the OSGi configuration from the OSGi Installer for component >> factories? >> Thanks, >> Konrad >> > > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected] >
