Issue 2811: Callback exception handler has potential name-clash (messaging-rtf) Source: IONA (Mr. Matthew Mihic, ) Nature: Severity: Summary: The rules for generating methods on callback interfaces can result in name clashes if the original interface has methods named "xxx" and "xxx_excep". I'd suggest avoiding this problem by appending a well-known suffix to both regular and exceptional callback operations (e.g. regular responses are handled by "xxx_complete", and exceptional responses are handled by "xxx_excep") Resolution: see below Revised Text: 1. In section 22.8.2 append the following paragraph: "If the name generated by the method described above clashes with a name that already exists in the interface, “_ami” strings are inserted immediately preceding the “_excep” repeatedly, until generated IDL operation name is unique in the interface. Actions taken: July 19, 1999: received issue May 13, 2002: closed issue Discussion: End of Annotations:===== Date: Thu, 20 Dec 2001 16:13:29 -0500 From: Jishnu Mukerji Organization: Hewlett-Packard Company X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: orb_revision@omg.org Subject: Proposed resolution for issue 2811 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by emerald.omg.org id fBKL41M22711 Content-Type: text/plain; charset=iso-8859-1 X-UIDL: WJgd9?S8!!:;T!!Oa6!! The following resolution will appear in a vote around the second week of January unless there is signficant technical objection. Jishnu. _____________________________________________________________________ Issue 2811: Callback exception handler has potential name-clash (messaging-rtf) Click here for this issue's archive. Source: IONA (Mr. Matthew Mihic, mmihic@iona.com ) Nature: Severity: Summary: The rules for generating methods on callback interfaces can result in name clashes if the original interface has methods named "xxx" and "xxx_excep". I'd suggest avoiding this problem by appending a well-known suffix to both regular and exceptional callback operations (e.g. regular responses are handled by "xxx_complete", and exceptional responses are handled by "xxx_excep") Resolution: Incorporate the same rule about inserting "_ami" repeatedly preceding the "_excep", until a unique name is obtained, as is used for sendp and sendc name munging. Revised Text: 1. In section 22.8.2 append the following paragraph: "If the name generated by the method described above clashes with a name that already exists in the interface , strings are inserted immediately preceding th e repeatedly, until generated IDL operation name is unique in the interface." Actions taken: Incorporate changes and close issue.