Issue 4557: What are the semantics of AlreadyBound in NamingContextExt::resolve_str() (naming_ftf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: In formal/01-02-65 the NamingContextExt::resolve_str() is defined as (pages 2-18 and A-3): Object resolve_str (in StringName sn) raises (NotFound, CannotProceed, InvalidName, AlreadyBound); The AlreadyBound exception listed in the raises clause appears superfluous. The spec does not say when or if the exception can be raised, and the text implies that it cannot be raised, because it reads: This is a convenience operation that performs a resolve in the same manner as NamingContext::resolve. It accepts a stringified name as an argument instead of a Name. However, the resolve() operation never raises AlreadyBound. It appears as if the exception in question should be removed from the raises clause. Resolution: already resolved Revised Text: Actions taken: September 5, 2001: received issue Discussion: End of Annotations:===== X-Authentication-Warning: doc.ece.uci.edu: Host doc.ece.uci.edu [128.195.174.34] claimed to be glamdring Message-ID: <015d01c13633$f50f7ef0$026fa8c0@glamdring> From: "Carlos O'Ryan" To: Subject: What are the semantics of AlreadyBound in NamingContextExt::resolve_str() Date: Wed, 5 Sep 2001 10:50:01 -0700 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Content-Type: text/plain; charset="iso-8859-1" X-UIDL: \F,!!need9d^Yd9WWVd9 Hi, In formal/01-02-65 the NamingContextExt::resolve_str() is defined as (pages 2-18 and A-3): Object resolve_str (in StringName sn) raises (NotFound, CannotProceed, InvalidName, AlreadyBound); The AlreadyBound exception listed in the raises clause appears superfluous. The spec does not say when or if the exception can be raised, and the text implies that it cannot be raised, because it reads: This is a convenience operation that performs a resolve in the same manner as NamingContext::resolve. It accepts a stringified name as an argument instead of a Name. However, the resolve() operation never raises AlreadyBound. It appears as if the exception in question should be removed from the raises clause. HTH -- Carlos O'Ryan (coryan@uci.edu) #include #include // "Speak softly and carry a megawatt laser" 1024D/46936992 33B3 C4ED AA90 FA0F E8D1 D509 FE5E 8F79 4693 6992 Date: Thu, 6 Sep 2001 06:27:01 +1000 (EST) From: Michi Henning To: Juergen Boldt cc: naming_ftf@emerald.omg.org Subject: Re: issue 4557 Naming FTF (???) issue In-Reply-To: <4.3.2.7.2.20010905163558.02e39c10@emerald.omg.org> Message-ID: Organization: IONA Technologies MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: @ma!!<~Qd9ZgB!!XWg!! On Wed, 5 Sep 2001, Juergen Boldt wrote: > This is issue # 4557 Carlos O'Ryan" > > This is an issue against the revised Naming Service, there is no > active > F/RTF. This issue has been logged with the inactive Naming FTF.... > > -Juergen > > What are the semantics of AlreadyBound in > NamingContextExt::resolve_str() > > In formal/01-02-65 the NamingContextExt::resolve_str() is > defined as > (pages 2-18 and A-3): > > Object resolve_str (in StringName sn) raises (NotFound, > CannotProceed, > InvalidName, AlreadyBound); This bug is already fixed in the new 2.5 version that's coming up. Cheers, Michi. -- Michi Henning +61 7 3324 9633 Chief CORBA Scientist +61 4 1118 2700 (mobile) IONA Technologies +61 7 3324 9799 (fax) Total Business Integration http://www.ooc.com.au/staff/michi X-Sender: juergen@emerald.omg.org X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 05 Sep 2001 16:54:23 -0400 To: Michi Henning From: Juergen Boldt Subject: Re: issue 4557 Naming FTF (???) issue Cc: naming_ftf@emerald.omg.org In-Reply-To: References: <4.3.2.7.2.20010905163558.02e39c10@emerald.omg.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-UIDL: D5R!!9aXd9V2J!!ZIfd9 Thanks Michi, based on this I close the issue... -Juergen At 06:27 AM 9/6/2001 +1000, Michi Henning wrote: Date: Thu, 6 Sep 2001 06:27:01 +1000 (EST) From: Michi Henning To: Juergen Boldt cc: naming_ftf@emerald.omg.org Subject: Re: issue 4557 Naming FTF (???) issue In-Reply-To: <4.3.2.7.2.20010905163558.02e39c10@emerald.omg.org> Message-ID: Organization: IONA Technologies MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: @ma!!<~Qd9ZgB!!XWg!! On Wed, 5 Sep 2001, Juergen Boldt wrote: > This is issue # 4557 Carlos O'Ryan" > > This is an issue against the revised Naming Service, there is no >active > F/RTF. This issue has been logged with the inactive Naming FTF.... > > -Juergen > > What are the semantics of AlreadyBound in >NamingContextExt::resolve_str() > > In formal/01-02-65 the NamingContextExt::resolve_str() is >defined as > (pages 2-18 and A-3): > > Object resolve_str (in StringName sn) raises (NotFound, >CannotProceed, > InvalidName, AlreadyBound); This bug is already fixed in the new 2.5 version that's coming up. Cheers, Michi. -- Michi Henning +61 7 3324 9633 Chief CORBA Scientist +61 4 1118 2700 (mobile) IONA Technologies +61 7 3324 9799 (fax) Total Business Integration http://www.ooc.com.au/staff/michi ================================================================ Juergen Boldt Senior Member of Technical Staff Object Management Group Tel. +1-781 444 0404 ext. 132 250 First Avenue, Suite 201 Fax: +1-781 444 0320 Needham, MA 02494, USA Email: juergen@omg.org URL: www.omg.org ================================================================