Issue 7281: For ExternalReferneceEndpoint add optional port name attribute (deployment-ftf) Source: PrismTech (Mr. Gerald Lee Bickle, jerry.bickle@prismtechusa.com) Nature: Uncategorized Issue Severity: Summary: For ExternalReferneceEndpoint add optional port name attribute to indicate the port that is used to connect to or to retrieve an interface from the ExternalReferenceEndpoint. Rationale for change is to allow for components to be connected to ExternalReferenceEndpoint that are components. An example is a SWRadio use case for an I/O device resident in the SWRadio, where the I/O Device has required and provider ports. Resolution: Revised Text: In section 6.10.3.1, add an optional "portName" attribute. In section 6.10.3.2, describe the optional portName attribute portName : String This optional attribute indicates, when specified, that the external entity referenced by the location attribute is a component, and further indicates which port of that component is to be connected. In section 6.10.3.4, indicate that if the provider boolean is false, the portName must be present. Actions taken: April 30, 2000: received issue May 9, 2005: closed issue Discussion: Resolution: Issue 7281 asks for a port name attribute to indicate, when the external entity being connected is a component, which port of the component should be used. This is necessary to connect to identified external components and when the global reference is to a user rather than a provider. Together with the resolution of issue 7080, this resolution properly enables global references to specify the intention to reference a service provider or service user, and if the intention is to reference a component, which port of that component is being referenced. End of Annotations:===== Date: Mon, 09 Aug 2004 10:31:29 -0400 From: James Kulp Organization: Mercury Computer Systems, Inc. User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en,pdf To: Andreas Hoffmann Cc: Deployment RTF Subject: Homework assignment for external endpoint issues: 7280, 7281 X-Virus-Scanned: by Clam AntiVirus External endpoints are the "global references" within an assembly that indicate an attachment to something outside the assembly, unrelated to the ports of the component being implemented by the assembly, and unrelated to any of the subcomponents within the assembly. Since an assembly is re-usable and implementation independent, such a global reference is inherently unmodular, much like an "extern" declaration buried inside a piece of C code. The purpose is to attach to something expected to somehow exist in every environment that the assembly implementation will execute in. Thus it is in some sense a "requirement" of the assembly implementation that such a reference be resolvable at execution time. An obvious example is "layered" deployment, where an initial layer will provide services to applications deployed "on top of" the lower "service layer" applications. Currently, external endpoints simply have a "location" attribute that allows connection to anything expressible in a URL. This includes predefined CORBA objects, name service queries, etc. (see section 13.6.10 of the CORBA 3.0 spec). Since CORBA object URLs are very extensible, restricting these endpoints in the PSM to be CORBA Object URLs as defined in 13.6.10 of CORBA provides a way to specify a wide variety of mechanisms to object the reference. Issue 7280 asks for a boolean to indicate whether the external entity being connected is a user or provider. Usually, the other endpoints of a connection imply what role is required for the ExternalEndpoint, but this is ambiguous in some cases. proposed solution: In section 6.10.3.1, add a "provider" boolean (consistent in naming and meaning to that in the ComponentPortDescription). In section 6.10.3.2, describe the "provider" boolean: provider : Boolean Indicates whether the intention is to connect to a provider of service (reference is to either an object or a component) or user of service (reference is to a component). Issue 7281 asks for a port name attribute to indicate, when the external entity being connected is a component, which port of the component should be used. This is necessary to connect to identified external components and when the global reference is to a user rather than a provider. proposed solution: In section 6.10.3.1, add an optional "portName" attribute. In section 6.10.3.2, describe the optional portName attribute portName : String This optional attribute indicates, when specified, that the external entity referenced by the location attribute is a component, and further indicates which port of that component is to be connected. In section 6.10.3.4, indicate that if the provider boolean is false, the portName must be present. These two solutions properly enable global references to specify the intention to reference a service provider or service user, and if the intention is to reference a component, which port of that component is being referenced. lReferneceEndpoint add optional port name attribute to indicate the port that is used to connect to or to retrieve an interface from the ExternalReferenceEndpoint. Rationale for change is to allow for components to be connected to ExternalReferenceEndpoint that are components. An example is a SWRadio use case for an I/O device resident in the SWRadio, where the I/O Device has required and provider ports.