Issue 6603: 6.4.17 ComponentPortDescription (02)                                                                                                                                                                    (deployment-ftf)
Source: PrismTech (Mr. Gerald Lee Bickle, jerry.bickle@prismtechusa.com)
Nature: Uncategorized Issue
Severity: 
Summary: The OLD CCM DTD and SCA had the concept of connection ID for a required
port.  This was useful when a required port allowed multiple connections to
it with the same interface, so it could distinguish the connection being to
it.  Add the flexibility in the Port definition of optional stating
connection ids for a required port and allow the component assembly
definition for a port connection to optional state a connection id to be
used. For a required port, instead of stating connection IDs, it could
optionally state the maximum number of connections per interface type for a
required port. When not stated it is assumed to be one.

Resolution: 
Revised Text: 
Actions taken:
November 12, 2003: received issue
May 9, 2005: closed issue
Discussion: 
During the meetings and telephone conferences of the previous FTF it has been agreed that this issue is to be closed without change. A new more specific issue with respect to connection endpoint's definition has been raised instead (7281).
End of Annotations:=====
ssue 2


The OLD CCM DTD and SCA had the concept of connection ID for a required
port.  This was useful when a required port allowed multiple connections to
it with the same interface, so it could distinguish the connection being to
it.  Add the flexibility in the Port definition of optional stating
connection ids for a required port and allow the component assembly
definition for a port connection to optional state a connection id to be
used. For a required port, instead of stating connection IDs, it could
optionally state the maximum number of connections per interface type for a
required port. When not stated it is assumed to be one.