| Summary: | [DataBinding] Make get<Value|Set|List|Map> methods of properties non-final | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Ovidio Mallo <mallo.ovidio> | ||||||
| Component: | UI | Assignee: | Ovidio Mallo <mallo.ovidio> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Ovidio Mallo <mallo.ovidio> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | bokowski, emoffatt, ob1.eclipse, pwebster, qualidafial, remy.suen | ||||||
| Version: | 3.6.1 | ||||||||
| Target Milestone: | 3.7 M5 | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Bug Depends on: | |||||||||
| Bug Blocks: | 306611 | ||||||||
| Attachments: |
|
||||||||
|
Description
Ovidio Mallo
After the discussion with Matthew in bug 306611, only the getter methods will be made non-final for now since for the setter it makes less sense. Created attachment 184650 [details]
patch which makes the getter non-final
Matthew, +1?
Let's add javadoc comments to the get<Value|List|Set|Map> methods to clarify: * What the method implementation does (checks for null and delegates to doGet<Value|List|Set|Map>) * Under what circumstances subclasses should override the default implementation (give alternative handling of nulls as an example). +1 once the above are addressed. Created attachment 184661 [details]
added the JavaDoc proposed by Matthew
Released to HEAD > 20101206 Hi Ovidio, I've talked to Boris, and could you please revert this fix. You can commit it again when 3.7 M4 is declared. PW The changes of this bug are reverted. Ovidio, you can push these changes again. Thanks for the reminder, Matthew. Re-released to HEAD > 20101223 |