Bug 134601 - NotationPackage does not resolve proxies
Summary: NotationPackage does not resolve proxies
Status: NEW
Alias: None
Product: GMF-Runtime
Classification: Modeling
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement
Target Milestone: ---   Edit
Assignee: Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-03 16:08 EDT by Pratik Shah CLA
Modified: 2010-07-19 12:29 EDT (History)
3 users (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 Pratik Shah CLA 2006-04-03 16:08:51 EDT 
Only a view's element gets resolved such that any subsequest view.getElement() invocations return the resolved element.

On the other hand, if an edge's target is a proxy, edge.getTarget() will always return the proxy (even after you've invoked ViewUtil.resolve(edge.getTarget()) successfully).

Test:
NotationPackage.eINSTANCE.getView_Element().isResolveProxies() returns true
NotationPackage.eINSTANCE.getView_TargetEdges().isResolveProxies() returns false
NotationPackage.eINSTANCE.getEdge_Source().isResolveProxies() returns false
NotationPackage.eINSTANCE.getEdge_Target().isResolveProxies() returns false

Apparently, this is affected by some setting used during EMF code generation.  Simply, invoking NotationPackage.eINSTANCE.getEdge_Target().setResolveProxies(true) does not help.
Comment 1 Steven R. Shaw CLA 2006-04-11 16:22:53 EDT 
Changing to enhancement request.  By current design, the assumption is that the source and target anchor's are in the same resource as the owning diagram.

To consider otherwise, requires a sweep of the code and a best practice around how clients should multiple diagram resources.
Comment 2 Eclipse Webmaster CLA 2010-07-19 12:29:54 EDT 
[GMF Restructure] Bug 319140 : product GMF and component
Runtime Diagram was the original product and component for this bug