Bug 128385

Summary:	[DataBinding] Debug bindings
Product:	[Eclipse Project] Platform	Reporter:	Aaron Digulla <digulla>
Component:	UI	Assignee:	Boris Bokowski <bokowski>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	djo, qualidafial
Version:	3.2	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Aaron Digulla

2006-02-17 06:53:58 EST

It's very hard to debug bindings; especially who updates/reads/writes/validates what and why.

To ease the pain, I suggest to add a Throwable to the classes which implement the actual binding. The Throwable should be initialized in the constructor when I use context.bind() so I can see later where a specific binding happened.

Comment 1 Peter Centgraf

2006-06-15 19:32:36 EDT

Is this resolved by IBindingListener and IBindingEvent?  Perhaps this bug should be closed....

Comment 2 Dave Orme

2006-06-23 16:42:04 EDT

This is a good idea.

Also suggest that IObservable classes do this and make this information available through an accessor.  Then as Peter suggests you could get this information in the BindingEvent...

Comment 3 Aaron Digulla

2007-08-10 04:30:04 EDT

Any updates on this bug? I'm wondering because it seems to be a five-minute job.

Comment 4 Matthew Hall

2007-10-29 19:46:08 EDT

Aaron, you may want to check out the sources into your workspace, make the changes you need (so you can move forward with your project), and contribute a patch back to the data binding project.

If this really is a 5-minute change, then coding it yourself would seem the most efficient approach for your need.

Comment 5 Eclipse Webmaster

2019-09-06 16:04:54 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.