| Summary: | [DataBinding] JavaBeanObservableValue does not generate correct ValueDiff when oldValue == newValue == null | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Matthew Hall <qualidafial> | ||||||
| Component: | UI | Assignee: | Matthew Hall <qualidafial> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | bokowski | ||||||
| Version: | 4.0 | ||||||||
| Target Milestone: | 3.5 M4 | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Matthew Hall
JavaBeanObservableMap and JavaBeanPropertyObservableMap also naively convert the PropertyChangeEvents into MapDiffs. The patch for 194734 eliminates this issue--leaving open in case we decide not to go that direction Retargeting for M3 Created attachment 117279 [details]
patch
Fixed bug in JavaBeanObservableMap, JavaBeanObservableValue, and JavaBeanPropertyObservableMap. The list and set implementations did not have the described bug.
Added tests to all JavaBeanObservable*Test classes just so we capture this requirement in the future.
Boris, +1?
Created attachment 117280 [details]
mylyn/context/zip
+1 looks good Released to HEAD > 20081111 (forgot to resolve bug at the time) Verified in I20090129-0100 by running test suite |