Issue 3176: Supporting TAG_MULTIPLE_COMPONENTS (interop) Source: Borland Software Corporation (Mr. Vishy Kasar, nobody) Nature: Uncategorized Issue Severity: Summary: I have a question on how can ORB vendor support profile with ID TAG_MULTIPLE_COMPONENTS? The spec 2.3/13.6.2 says single profile holds enough information to drive a complete invocation. Let us say we have an IOR with one profile and the ID is TAG_MULTIPLE_COMPONENTS. As per 13.6.2.2, the profile body in this case contains a MultipleComponentProfile. Let us again assume that there is only one TaggedComponent with component id of TAG_CODE_SETS and its component data. What we have here is a legal profile with no end point information. What can a ORB do with such a profile? Is there any thing broken here or did I just misinterpret the spec completely? Resolution: Close with no revision Revised Text: Actions taken: January 4, 2000: received issue October 4, 2000: closed issue Discussion: When the spec says that a single profile holds enough information to drive a complete invocation, it means two things: 1. Each profile is exclusive. The ORB should not combine information from more than one profile when binding to the object implementation. 2. Each profile must stand alone. A profile is broken if it does not contain enough information to complete an invocation. This is where the above example IOR fails. End of Annotations:===== Sender: "Vishy Kasar" Message-ID: <38725377.9390BF6C@inprise.com> Date: Tue, 04 Jan 2000 12:09:27 -0800 From: Vishy Kasar Organization: Inprise Corporation - Visibroker Development X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: interop@omg.org Subject: Supporting TAG_MULTIPLE_COMPONENTS Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: m'#!!'dZ!![1!!!~C;e9 Hi, I have a question on how can ORB vendor support profile with ID TAG_MULTIPLE_COMPONENTS? The spec 2.3/13.6.2 says single profile holds enough information to drive a complete invocation. Let us say we have an IOR with one profile and the ID is TAG_MULTIPLE_COMPONENTS. As per 13.6.2.2, the profile body in this case contains a MultipleComponentProfile. Let us again assume that there is only one TaggedComponent with component id of TAG_CODE_SETS and its component data. What we have here is a legal profile with no end point information. What can a ORB do with such a profile? Is there any thing broken here or did I just misinterpret the spec completely? -- Cheers! Sender: jbiggar@corvette.floorboard.com Message-ID: <387264CC.C14D52AB@floorboard.com> Date: Tue, 04 Jan 2000 13:23:24 -0800 From: Jonathan Biggar X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Vishy Kasar CC: interop@omg.org Subject: Re: Supporting TAG_MULTIPLE_COMPONENTS References: <38725377.9390BF6C@inprise.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: VCQd999U!!^\kd9#4$!! Vishy Kasar wrote: > > Hi, > > I have a question on how can ORB vendor support profile with ID > TAG_MULTIPLE_COMPONENTS? The spec 2.3/13.6.2 says single profile > holds > enough information to drive a complete invocation. Let us say we > have an > IOR with one profile and the ID is TAG_MULTIPLE_COMPONENTS. As per > 13.6.2.2, the profile body in this case contains a > MultipleComponentProfile. Let us again assume that there is only one > TaggedComponent with component id of TAG_CODE_SETS and its component > data. > > What we have here is a legal profile with no end point > information. What > can a ORB do with such a profile? Is there any thing broken here or > did > I just misinterpret the spec completely? When the spec says that a single profile holds enough information to drive a complete invocation, it means two things: 1. Each profile is exclusive. The ORB should not combine information from more than one profile when binding to the object implementation. 2. Each profile must stand alone. A profile is broken if it does not contain enough information to complete an invocation. This is where your example IOR fails. -- Jon Biggar Floorboard Software jon@floorboard.com jon@biggar.org