Issue 494: IDL Type Extensions: DATA_CONVERSION exception (idltx) Source: (, ) Nature: Uncategorized Severity: Summary: Summary: Algorithm on p. 27 says to raise DATA_CONVERSION exception, but textual description on p. 28 par 1 specifies CODESET_INCOMPATIBLE exception when client and server native codesets aren"t compatible Resolution: resolved is current 2.3 draft, closed issue Revised Text: Actions taken: February 4, 1997: received issue May 6, 1999: closed issue Discussion: End of Annotations:===== Return-Path: From: jfh@hal.com (Jim Hughes) Date: Mon, 2 Jun 1997 11:59:11 -0700 (PDT) To: leou@austin.ibm.com Cc: rabin@osf.org, idltx@omg.org, newcombe@austin.ibm.com, nick@stlvm20.rscs, hari@austin.ibm.com, orb_revision@omg.org, linda@omg.org Subject: Re[2]: CODESET_INCOMPATIBLE exception Leo, Frankly, I wasn't sure of the process for resolving these issues, but since IBM is taking the lead to resolve them, let me provide my suggested resolutions and suggest we get confirmation from the rest of the IDL Extensions RTF: Issue 494: The error is valid, and the correction should be: replace "DATA_CONVERSION" in the second to last line of the algorithm on page 27 (ptc/97-01-01) with "CODESET_INCOMPATIBLE". This matches the text in the first paragraph on page 28. If the RTF confirms this correction, then I suggest IBM notify Linda Heaton to simply make the correction in the edited copy. Return-Path: To: idltx@omg.org Cc: nicktindall@vnet.ibm.com Reply-To: leou@austin.ibm.com Subject: IDL Type Extensions Issues 494 and 495 resolution Date: Wed, 04 Jun 97 09:52:39 -0500 From: Leo Uzcategui In the interest of closing these issues and getting the changes in the CORBA Core revision cycle, here's the proposed resolution. Unless I hear any objections, I'll assume everyone agrees and I'll ask Linda Heaton (OMG) to make changes in the edited documents and ask Paul Rabin to include in the Core RTF corrections. (I believe the deadline is June 20.) Issue 494: DATA_CONVERSION exception Algorithm on p. 27 (ptc/97-01-01) says to raise DATA_CONVERSION exception, but textual description on p. 28 paragraph 1 specifies CODESET_INCOMPATIBLE exception when client and server native codesets aren't compatible Proposed resolution: replace DATA_CONVERSION with CODESET_INCOMPATIBLE