Community
Participate
Working Groups
Currently, when the registry is notifying the IRegistryChangeListener, it does not wrap the call in try-catch block (or in ISafeRunnable). This leads to the problem if one registry listener throws an exception, the registry stops notifying the listeners. If the bad listener is first in the row, nobody will be notified.
Created attachment 68165 [details] proposal fix Here is a proposal fix for the bug. It is rather straight forward. I used SafeRunner because it directly logs to the log if available. Additionally the exception is added to the result status returned by processChangeEvent() so anyone interested in it could check it out (currently no one:)
+1 to the patch. Adding Pascal to review. Thank you!
Patch is good to go. While releasing, make sure you update the copyrights appropriately.
err, you need another review
The contributed patch is released into CVS head; copyright is updated - thanks Pascal for reminder!