Issue 7286: ComponentExternalPortEndpoint definition is not unique enough                                                                                                                                           (deployment-ftf)
Source: PrismTech (Mr. Gerald Lee Bickle, jerry.bickle@prismtechusa.com)
Nature: Uncategorized Issue
Severity: 
Summary: ComponentExternalPortEndpoint definition is not unique enough.  A
component can have the same port name. This definition needs to be
qualified by a component as done for SubcomponentPortEndpoint.

Resolution: 
Revised Text: 
Actions taken:
April 30, 2000: received issue
May 9, 2005: closed issue
Discussion: 
During the meetings and telephone conferences of the RTF it has been agreed that this issue is to be closed without change.

The ComponentExternalPortEndpoint element always identifies a port of the component interface that is implemented by this assembly-based component implementation.

The port type is well-defined by the component interface; its Component- InterfaceDescription is available via the "implements" association of the ComponentImplementationDescription element that the ComponentAssembly- Description is embedded in.

There is no conflict with names of subcomponent ports. The namespace for ports and properties of each subcomponent instance is distinct from the namespace for ports and properties of the assembly-based component implementation itself.


Disposition:	Closed, no change


End of Annotations:=====
omponentExternalPortEndpoint definition is not unique enough.  A
component can have the same port name. This definition needs to be
qualified by a component as done for SubcomponentPortEndpoint.