Community
Participate
Working Groups
When things go wrong in DataBinding, they are hard to catch. I do understand that the basic approach of binding makes the usual propagation of exceptions up the calling stack difficult (useless, who would catch it?), and that the ValidationStatus (IStatus) should be checked by e.g. a UI, but would argue that simply also providing more logging exceptions as error when caught inside Data Binding couldn't hurt and would help in development. More specifically, I would suggest logging the Exception caught in org.eclipse.core.databinding.UpdateValueStrategy#doSet(), and related similar methods such as UpdateListStrategy's doAdd() & doMove() & doReplace() as well as UpdateSetStrategy's doAdd() & doRemove(). Logging "Framework" chosen probably wouldn't be slfj4j or similar API, but DataBinding's own Policy.getLog().log(new Status(IStatus.ERROR, Policy.JFACE_DATABINDING, 0, "..." / e.getMessage()?, e)); as elsewhere in the DataBinding codebase. If you think this idea is of interest and prefer getting a concrete patch proposal / GitHub pull request instead of the textual proposal above, please let me know and I'll contribute one.
*** Bug 483172 has been marked as a duplicate of this bug. ***
Patches are welcome.
Conrad told me that he is working on a patch.
New Gerrit change created: https://git.eclipse.org/r/63294
Can someone please review the change?
I would really appreciate if someone reviews this change.
Gerrit change https://git.eclipse.org/r/63294 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=5abd737b67125b8d85293f480f10b0fdc5b800a9
Thanks for this patch, Conrad. I think a lot of users have been missing these exception logging, since they we somehow suppressed beforehand.