Issue 7284: ExternalReferneceEndpoint need to indicate the type of interface                                                                                                                                        (deployment-ftf)
Source: PrismTech (Mr. Gerald Lee Bickle, jerry.bickle@prismtechusa.com)
Nature: Uncategorized Issue
Severity: 
Summary: SubcomponentPortEndpoint, ComponentExternalPortEndpoint, and
ExternalReferneceEndpoint need to indicate the type of interface.
Rational: UML 2.0 defines ports that can be associated with many required
and provider interfaces
Resolution: 
Revised Text: Add a supportedType attribute to the ExternalReferenceEndpoint class: 

supportedType: String [1..*] The interface type of the external 
endpoint being connected. For user endpoints, the set of types required by the using entity: connect a user requiring any one of these types.  For provider endpoints, the set of types required to be supported by the connected provider.

Actions taken:
April 30, 2000: received issue
May 9, 2005: clsoed issue
Discussion: 
Resolution:
The second part body of this issue describes a different problem than the title and the first sentence of this issue. Thus the RTF decided to split this issue into two parts:

1st part: The issue with the current issue number covering the title of this issue.

2nd part:  A separate issue with number 7877 has been raised covering the second part of the issue's body reading

"Rationale: UML 2.0 defines ports that can be associated with many required and provider interfaces."

to be resolved separately by this new issue.

Again, the following resolution covers only the 1st part of this issue as described above.
For SubcomponentPortEndpoint, the type(s) are obtained by navigating to the ComponentInterfaceDescription.  For ComponentExternalPortEndpoint, the type(s) are obtained by navigating to the ComponentInterfaceDescription. 
For ExternalReferenceEndpoint, the types are indeed missing, thus a "supportedType" attribute is added to the ExternalReferenceEndpoint class. This allows assembly tools to validate the type compatibility of connections that involve an external reference endpoint. 

End of Annotations:=====
ubcomponentPortEndpoint, ComponentExternalPortEndpoint, and
ExternalReferneceEndpoint need to indicate the type of interface.
Rational: UML 2.0 defines ports that can be associated with many required

Date: Tue, 07 Dec 2004 17:25:04 -0500 
From: James Kulp <jek@mc.com> 
Organization: Mercury Computer Systems, Inc. 
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910 
X-Accept-Language: en,pdf 
To: Deployment RTF <deployment-rtf@omg.org> 
Subject: Homework: Issue resolution for what is left of 7284 after UML 2 moved 
 to 7877 
X-Virus-Scanned: by ClamAV at mailsnare.net 


Given that 7877 addresses the UML 2.0 issues of a port taking both user and provider
roles, here is a proposed resolution to the remainder of this issue:


SubcomponentPortEndpoint, ComponentExternalPortEndpoint, and
ExternalReferneceEndpoint need to indicate the type of interface.


For SubcomponentPortEndpoint, the type(s) are obtained by navigating to the
ComponentInterfaceDescription.
For ComponentExternalPortEndpoint, the type(s) are obtained by navigating to the
ComponentInterfaceDescription.
For ExternalReferenceEndpoint, the types are indeed missing, thus, the solution is:


Add a requiredType attribute to the ExternalReferenceEndpoint class:


requiredType: String[1..*] The interface type of the external endpoint being connected.  For user endpoints,
the set of types required by the using entity: connect a user requiring any one of these types.  For provider endpoints, the set of types required to be supported by the connected provider.





Issue 7284 Proposed Resolution
2005-01-05
Issue Description
SubcomponentPortEndpoint, ComponentExternalPortEndpoint, and ExternalReferenceEndpoint need to indicate the type of interface.  Rational: UML 2.0 defines ports that can be associated with many required and provider interfaces.
Recommendation
Close, no change.  6602 restricts ports to have one interface in each direction, and external ports could have multiple interfaces (just like internal ports) in any case.
and provider interfaces