Issue 14896: Update the GCM ClientServerPort to take into account evolutions in UML 2.3 (marte-rtf)
Source: THALES (Mr. Sebastien Demathieu, sebastien.demathieu(at)thalesgroup.com)
Nature: Revision
Severity: Minor
Summary: Update the GCM ClientServerPort to take into account evolutions in UML 2.3 (introduction of conjugated port)
Resolution: The issue refers to the introduction in UML 2.3 of the property “isConjugated” on the metaclass
Port. It means that the property “isConjugated” is no longer needed on the stereotype
“ClientServerPort” from MARTE since ClientServerPort extends Port.
The revised text describes required modifications to the MARTE specification. Note that, even
though the issue does not mention it, FlowPort are also concerned by this evolution of UML ports.
The “revised text” section also describes modifications required by the stereotype FlowPort.
Revised Text: see pages 76 - 77 of ptc/2010-08-30 for resolution
Actions taken:
December 31, 2009: received issue
January 14, 2011: closed issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 31 Dec 2009 07:34:42 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:          Séstien Demathieu
Company:       Thales
mailFrom:      sebastien.demathieu@thalesgroup.com
Notification:  Yes
Specification: MARTE
Section:       GCM
FormalNumber:  09-11-02
Version:       1.0
RevisionDate:  11/2009
Page:          147
Title:         Update the GCM ClientServerPort to take into account evolutions in UML 2.3
Nature:        Revision
Severity:      Minor
test:          3qw8
B1:            Report Issue


Description:

Update the GCM ClientServerPort to take into account evolutions in UML 2.3 (introduction of conjugated port)