Recognize OSGi bundle resource in ConfigurationWatchList.convertToFile
Hi, The current implementation of ConfigurationWatchList.convertToFile returns null when the URL type is not file. Due to this automatic reloading on change of configuration does not work in OSGi bundles. This problem occurs even if you use a fragment. As in any case, the logback.xml file will be recognized as bundleresource type and not as file type. This is necessary as the logback.xml config file is recognized during the start up time. So, it creates confusion as the file is found first time around and then the reloading does not occur. And, this is not mentioned in the documentation either. Given that logback has a p2 repository for OSGi support, IMHO this feature is a must. BTW I would love to contribute this feature. Regards, Ashwin
Ashwin, I don't have any interest in OSGI myself. But a creating a fix and submitting a pull request might be the fastest way to get this resolved. As then others with and interest can review it. Thanks David
On 9 Jun 2014, at 18:53, Ashwin Jha <ajha.dev@gmail.com> wrote:
Hi,
The current implementation of ConfigurationWatchList.convertToFile returns null when the URL type is not file. Due to this automatic reloading on change of configuration does not work in OSGi bundles.
This problem occurs even if you use a fragment. As in any case, the logback.xml file will be recognized as bundleresource type and not as file type. This is necessary as the logback.xml config file is recognized during the start up time. So, it creates confusion as the file is found first time around and then the reloading does not occur. And, this is not mentioned in the documentation either. Given that logback has a p2 repository for OSGi support, IMHO this feature is a must.
BTW I would love to contribute this feature.
Regards, Ashwin
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user
participants (2)
-
Ashwin Jha -
David Roussel