Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334730 - Name conflict with Object#notify()
Summary: Name conflict with Object#notify()
Status: VERIFIED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: Tools (show other bugs)
Version: 2.7.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 minor (vote)
Target Milestone: M5   Edit
Assignee: Ed Merks CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-18 23:08 EST by Kenn Hussey CLA
Modified: 2011-01-23 22:10 EST (History)
0 users

See Also:
Kenn.Hussey: indigo+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kenn Hussey CLA 2011-01-18 23:08:28 EST 
The generated edit code for the GWT runtime platform contains a plugin images class (e.g., TreeEditPluginImages) which has a method for each type that corresponds to its image resource (icon). However, a model containing a class named 'Notify' will result in a 'notify()' method, which conflicts with the method of the same signature in Object.

Please add appropriate name mangling (as is done with other Java keywords) so that this conflict does not occur, e.g., so that the method has a signature of 'notify_()' instead. Other potential conflicts should probably be addressed as well, e.g., for classes named Clone, Wait, HashCode, etc..
Comment 1 Ed Merks CLA 2011-01-21 02:19:27 EST 
The fix is committed to CVS for 2.7.
Comment 2 Kenn Hussey CLA 2011-01-23 22:10:56 EST 
An integration build containing the fix is available.