Bug 140178 - [Commands] there should be no calls to resolve semantic element
Summary: [Commands] there should be no calls to resolve semantic element
Status: REOPENED
Alias: None
Product: GMF-Runtime
Classification: Modeling
Component: General (show other bugs)
Version: 1.0   Edit
Hardware: PC Windows XP
: P3 normal
Target Milestone: 2.1   Edit
Assignee: Anthony Hunter CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2006-05-04 11:16 EDT by Mohammed Mostafa CLA
Modified: 2010-07-19 21:59 EDT (History)
1 user (show)

See Also:

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 Mohammed Mostafa CLA 2006-05-04 11:16:30 EDT 
The fact that the Element EStructural Feature had its ResolveProxies flag set to true means that no clients should ever need to call resolve semantic element, because if getElement returns a proxy this means it is irresolvable and trying to resolve it again will be just a waste of time cause it will fail again.
This will have a bad impact on performance when the semantic element of the view is irresolvable.
Comment 1 Mohammed Mostafa CLA 2006-07-12 13:35:54 EDT 
re-assigne to Yaser based on his request
Comment 2 Yasser Lulu CLA 2006-08-10 14:26:56 EDT 
re-assigne back to Mohammed based on his request.
Comment 3 Mohammed Mostafa CLA 2006-08-10 15:10:44 EDT 
moving to 2.0
Comment 4 Anthony Hunter CLA 2007-06-19 11:19:58 EDT 
Moving to the next release, GMF 2.1.
Comment 5 Anthony Hunter CLA 2007-06-20 09:38:04 EDT 
Closed based on Yaser's work at the end of the 1.0 release.
Comment 6 Mohammed Mostafa CLA 2007-06-20 09:40:00 EDT 
This had not been resolved; the issue is still there
Comment 7 Eclipse Webmaster CLA 2010-07-19 21:59:33 EDT 
[GMF Restructure] Bug 319140 : product GMF and component
Runtime was the original product and component for this bug