Issue 3263: Inadequate error codes for NamingContextExt (naming_ftf) Source: Cisco Systems (Mr. Paul Kyzivat, pkyzivat@cisco.com) Nature: Uncategorized Issue Severity: Summary: Consider the following situation: - Two naming servers: One is new and implements NamingContextExt. The other is old and only implements the old NamingContext interface. - the old one is federated into the new one - a client invokes an operation in the extended interface, on the new one, using a compound name that references the old one. It is not clear what exception should be returned in this case. There seem a couple of semi-reasonable candidates: CannotProceed & NO_IMPLEMENT. Resolution: withdrawn by submitter Revised Text: Actions taken: January 31, 2000: received issue February 7, 2000: closed issue Discussion: End of Annotations:===== Date: Mon, 31 Jan 2000 16:18:20 -0500 From: Paul H Kyzivat Organization: NobleNet X-Mailer: Mozilla 4.0 [en] (WinNT; I) MIME-Version: 1.0 To: issues@omg.org CC: Naming FTF Subject: Inadequate error codes for NamingContextExt X-Priority: 3 (Normal) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: kN>e9ddV!!_Xi!!d]Yd9 Status: U Consider the following situation: - Two naming servers: One is new and implements NamingContextExt. The other is old and only implements the old NamingContext interface. - the old one is federated into the new one - a client invokes an operation in the extended interface, on the new one, using a compound name that references the old one. It is not clear what exception should be returned in this case. There seem a couple of semi-reasonable candidates: CannotProceed & NO_IMPLEMENT. Date: Tue, 1 Feb 2000 10:36:54 +1000 From: Ted McFadden To: Paul H Kyzivat Cc: issues@omg.org, Naming FTF Subject: Re: Inadequate error codes for NamingContextExt Message-ID: <20000201103654.A15323@ooc.com.au> Mail-Followup-To: Paul H Kyzivat , issues@omg.org, Naming FTF References: <3895FC1C.5106221E@roguewave.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0i In-Reply-To: <3895FC1C.5106221E@roguewave.com>; from paulk@roguewave.com on Mon, Jan 31, 2000 at 04:18:20PM -0500 Content-Type: text/plain; charset=us-ascii X-UIDL: 2JSd97!Fe90J=!!]1)e9 Status: U On Mon, Jan 31, 2000 at 04:18:20PM -0500, Paul H Kyzivat wrote: > Consider the following situation: > > - Two naming servers: > One is new and implements NamingContextExt. > The other is old and only implements the old NamingContext > interface. > > - the old one is federated into the new one > > - a client invokes an operation in the extended interface, > on the new one, using a compound name that references the old one. > > It is not clear what exception should be returned in this case. > > There seem a couple of semi-reasonable candidates: > CannotProceed & NO_IMPLEMENT. Why would an exception need to be returned? resolve_str is the only operation on NamingContextExt that would involve federation. For resolve_str the string is converted to a name in the first naming_context, so the federated calls are all to resolve. If there is some advantage to an implementation passing a resolve_str on, that's ok. But the NamingContextExt implementation must catch the resulting exception and retry is with a resolve. Cheers, Ted. -- Ted McFadden tmcf@ooc.com.au Object Oriented Concepts http://www.ooc.com Suite 4 904 Stanley St. +61-7-3891-5744 East Brisbane 4169, QLD. Australia From: Paul Kyzivat To: "'Ted McFadden'" Cc: Naming FTF , "Juergen Boldt (E-mail)" Subject: RE: Inadequate error codes for NamingContextExt Date: Tue, 1 Feb 2000 09:18:27 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" X-UIDL: cp#e93~id9:j?!!=H1e9 Ted, You are right - it is stupid non-issue. I was thinking about the federate-able style operations, but of course there aren't any of that sort in NamingContextExt. Paul Jurgen - please just consider this issue withdrawn. > -----Original Message----- > From: Ted McFadden [mailto:tmcf@ooc.com.au] > Sent: Monday, January 31, 2000 7:37 PM > To: Paul H Kyzivat > Cc: issues@omg.org; Naming FTF > Subject: Re: Inadequate error codes for NamingContextExt > > > On Mon, Jan 31, 2000 at 04:18:20PM -0500, Paul H Kyzivat wrote: > > Consider the following situation: > > > > - Two naming servers: > > One is new and implements NamingContextExt. > > The other is old and only implements the old > NamingContext interface. > > > > - the old one is federated into the new one > > > > - a client invokes an operation in the extended interface, > > on the new one, using a compound name that references the old > one. > > > > It is not clear what exception should be returned in this case. > > > > There seem a couple of semi-reasonable candidates: > > CannotProceed & NO_IMPLEMENT. > > Why would an exception need to be returned? > > resolve_str is the only operation on NamingContextExt that > would involve federation. > > For resolve_str the string is converted to a name in the first > naming_context, so the federated calls are all to resolve. > > If there is some advantage to an implementation passing a > resolve_str on, that's ok. But the NamingContextExt > implementation must catch the resulting exception and > retry is with a resolve. > > > > Cheers, > Ted. > > > > > -- > Ted McFadden tmcf@ooc.com.au > Object Oriented Concepts http://www.ooc.com > Suite 4 904 Stanley St. +61-7-3891-5744 > East Brisbane 4169, QLD. Australia >