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

Bug 358051

Summary: ConnectorOperations validation rules should test for interface compatibility rather than identity
Product: [Modeling] MDT.UML2 Reporter: Alexander Nyßen <nyssen>
Component: CoreAssignee: UML2 Inbox <mdt-uml2-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: major    
Priority: P3 CC: patrick.koenemann
Version: 3.2.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Alexander Nyßen CLA 2011-09-19 02:16:39 EDT 
The validation rules implemented within ConnectorOperations do check for identity of interfaces instead of signature compatibility. This is too strict, according to UML2 superstructure, Section 8.3.2, Paragraph Constraints, the following holds:

[3]	If a delegation connector is defined between a source Interface or Port and a target Interface or Port, then the target Interface must support a signature compatible subset of Operations of the source Interface or Port.

[4]	In a complete model, if a source Port has delegation connectors to a set of delegated target Ports, then the union of the Interfaces of these target Ports must be signature compatible with the Interface that types the source Port.

Thus, the methods within ConnectorOperations should be reimplemented to test for signature compatibility of operations instead.
Comment 1 Kenn Hussey CLA 2011-09-24 10:35:26 EDT 
These constraints no longer exist in UML 2.4 (to be supported by UML2 4.0)...
Comment 2 Kenn Hussey CLA 2012-06-14 15:40:48 EDT 
Now that the Indigo service releases are done and UML2 4.0, which supports UML 2.4.1 (where these constraints no longer exist), is about to be released, it's not likely we'll go back and fix this issue.