Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351631 - Validations to avoid bad code for setting delegate
Summary: Validations to avoid bad code for setting delegate
Status: CLOSED DUPLICATE of bug 386050
Alias: None
Product: EMF
Classification: Modeling
Component: Core (show other bugs)
Version: 2.7.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Ed Merks CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-09 10:57 EDT by Ed Willink CLA
Modified: 2013-01-10 08:28 EST (History)
0 users

See Also:

Attachments
Demonstration project (3.39 KB, application/x-download)
2011-07-09 10:57 EDT, Ed Willink CLA 		no flags Details
View All 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 Ed Willink CLA 2011-07-09 10:57:58 EDT 
Created attachment 199373 [details]
Demonstration project

The attached project gives two errors when genmodeled. The errors go away after regenmodeling without the setting delegate.

The first problem is a missing default initial value constant. This also goes away if the attribute is set non-changeable. Perhaps there should be a validation warning for a changeable setting delegate.

The second problem is the use of the attribute's field in toString(), even though the field does not exist. This also goes away if the attribute is set volatile. Perhaps there should be a validation warning for a non-volatile setting delegate.
Comment 1 Ed Merks CLA 2013-01-10 08:28:53 EST 

*** This bug has been marked as a duplicate of bug 386050 ***