Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 296756

Summary: ConnectionEndHandle creates a new Handle at the source of the connection
Product: [Tools] GEF Reporter: josch <js.abc>
Component: GEF-Legacy GEF (MVC)Assignee: Anthony Hunter <ahunter.eclipse>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: ahunter.eclipse
Version: 3.5   
Target Milestone: 3.6.0 (Helios) M5   
Hardware: PC   
OS: Windows Vista   
Whiteboard:

Description josch CLA 2009-12-02 17:10:22 EST
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 GTB6 (.NET CLR 3.5.30729)
Build Identifier: 3.5

All constructors are wrong. Example:

public ConnectionEndHandle(ConnectionEditPart owner) {
	super(owner, ConnectionLocator.SOURCE);
}

Correct:
public ConnectionEndHandle(ConnectionEditPart owner) {
	super(owner, ConnectionLocator.TARGET);
}

Workaround:
use 
new ConnectionEndpointHandle( connectionEditPart, ConnectionLocator.TARGET )

Reproducible: Always
Comment 1 Anthony Hunter CLA 2010-01-05 10:28:21 EST
This problem was introduced with Bug 212935 .

I imagine most users moved to using ConnectionEndpointHandle since ConnectionEndHandle is deprecated anyway.

Still fixed in 3.6 to be backward compatible.