Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338947 - renaming an attribute in a class with an error causes 3 prompts to appear
Summary: renaming an attribute in a class with an error causes 3 prompts to appear
Status: ASSIGNED
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: Diagram Editor (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: Petya Sabeva CLA
QA Contact: Stefan Dimov CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-04 10:41 EST by Karen Butzke CLA
Modified: 2015-05-14 14:11 EDT (History)
2 users (show)

See Also:

Attachments
patch (4.69 KB, patch)
2011-05-05 09:57 EDT, Petya Sabeva CLA 		no flags Details | Diff
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 Karen Butzke CLA 2011-03-04 10:41:06 EST 
I have 1 entity with 1 attribute that has a validation error saying the table can't be found on the database. In the JPA diagram editor I rename the attribute and I am prompted : 'code modification may not be accurate as affected resource '<name>' has compile errors'. This prompt appears 3 times, I assume once for renaming the attribute, once for renaming the getter, and once for renaming the setter.
Comment 1 Petya Sabeva CLA 2011-05-05 09:57:36 EDT 
Created attachment 194831 [details]
patch
Comment 2 Stefan Dimov CLA 2011-05-10 07:51:34 EDT 
The fix doesn't consider the property based access entity might have no fields, but just getters
Comment 3 Stefan Dimov CLA 2011-05-12 07:54:34 EDT 
Neil, what about this one? Should I propose it for PMC review? Appearing of the three prompts is annoying, but not a show stopper. On the other hand, the fix is relatively small and the risk - low.
Comment 4 Neil Hauge CLA 2011-05-12 11:30:04 EDT 
I think we can safely wait on this one.
Comment 5 Neil Hauge CLA 2011-10-27 11:16:38 EDT 
The 3.2 target now represents the Juno release.
Comment 6 Petya Sabeva CLA 2012-05-04 02:02:14 EDT 
Retargeting this bug to the Kepler realease (3.3).
Comment 7 Petya Sabeva CLA 2013-05-08 07:56:36 EDT 
Retargeting this bug to 3.4 release.
Comment 8 Neil Hauge CLA 2014-09-30 16:56:50 EDT 
Bulk move to Dali 3.5 as Dali 3.4 has shipped.
Comment 9 Neil Hauge CLA 2015-05-14 14:11:28 EDT 
Deferring from 3.5 to Future target.