Bug 183812

Summary:	Consider opposite references when creating links
Product:	[Modeling] GMF-Tooling (ARCHIVED)	Reporter:	Dmitry Stadnik <dimzzy>
Component:	Core	Assignee:	Artem Tikhomirov <tikhomirov.artem>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	boris.blajer, erik.verbruggen, kototamo
Version:	unspecified	Keywords:	test
Target Milestone:	2.2
Hardware:	All
OS:	All
Whiteboard:

Description Dmitry Stadnik

2007-04-24 11:33:52 EDT

from the newsgroup:

I've got a class A in my model that can reference one class B. The class B can also reference zero or one A, and EOpposite are set in each class so that linking A to B set up correctly the references.

However, I can link two different instances of A to my class B without errors in GMF.

Comment 1 Mohammed Mostafa

2007-04-24 13:01:28 EDT

*** Bug 183786 has been marked as a duplicate of this bug. ***

Comment 2 Artem Tikhomirov

2008-07-03 08:37:38 EDT

Done in HEAD.

Lite runtime already had the check generated, with a subtle difference from what I did for the FullRT: if eOpposite is derived, no check is generated. Since I'm unaware of cases when it might be useful, I decided to not respect isDerived for now.

Tests: LinkEcoreConstraintsTest#testOppositeBounds

Comment 3 Eclipse Webmaster

2010-07-16 23:35:05 EDT

[target cleanup] 2.2 M1 was the original target milestone for this
bug

Comment 4 Eclipse Webmaster

2010-07-19 22:18:30 EDT

[GMF Restructure] Bug 319140 : product GMF and component
Generation was the original product and component for this bug