Guten Tag Nandan S, am Donnerstag, 10. April 2014 um 10:43 schrieben Sie: > Loggers will be deleted/added from configuration file manually.
And that's the point: There's no logic or API to delete loggers and during reloading a configuration file the repository is not automatically reset, which means changes are only added or existing objects reconfigured. Deleted loggers are not recognized as such and stay in the repo. The only option you seem to have is to do as I said before: Override the used file watcher and reset the repo on your own. This way each reload of the configuration file starts newly from scratch. I'm pretty sure there won't be any other solution in the near future, because there are too many open questions to answer: One needs to recognize deleted objects from the configuration and delete those from the repository, but they might still be in use somewhere around an application etc. This doesn't sound like an easy task. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
