Issue 2620: CODESET_INCOMPATIBLE exception (interop) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: if a code set negotiation fails the CORBA 2.3 specfication says that a CODESET_INCOMPATIBLE exception is to be raised. There doesn"t seem to be any further reference to a CODESET_INCOMPATIBLE exception elsewhere. So where is the CODESET_INCOMPATIBLE exception defined? Or should it read INV_OBJREF? Resolution: Revised Text: Actions taken: April 22, 1999: received issue April 26, 1999: moved from C++ to interop April 28, 1999: closed issue Discussion: closed End of Annotations:===== From: us@ooc.de (Uwe Seimet) Subject: CODESET_INCOMPATIBLE exception To: orbos@omg.org Date: Wed, 21 Apr 1999 14:37:57 -0100 Hi, if a code set negotiation fails the CORBA 2.3 specfication says that a CODESET_INCOMPATIBLE exception is to be raised. There doesn't seem to be any further reference to a CODESET_INCOMPATIBLE exception elsewhere. So where is the CODESET_INCOMPATIBLE exception defined? Or should it read INV_OBJREF? Take care Uwe -- ------------------------------------------------------------------ Dr. Uwe Seimet Tel.: +49 7243 12210 Object-Oriented Concepts GmbH Fax: +49 7243 12216 E-Mail: mailto:us@ooc.de http://www.ooc.de Sender: jis@fpk.hp.com Date: Wed, 21 Apr 1999 12:19:42 -0400 From: Jishnu Mukerji Organization: Hewlett-Packard EIAL To: interop@omg.org CC: Uwe Seimet , cxx_revision@omg.org, issues@omg.org, orb_revision@omg.org Subject: Re: CODESET_INCOMPATIBLE exception References: <99Apr21.145641gmt-0100.27780@bam.bruker.de> Uwe Seimet wrote: > > Hi, > > if a code set negotiation fails the CORBA 2.3 specfication says that > a > CODESET_INCOMPATIBLE exception is to be raised. There doesn't seem > to be > any further reference to a CODESET_INCOMPATIBLE exception > elsewhere. So > where is the CODESET_INCOMPATIBLE exception defined? Or should it > read > INV_OBJREF? I was wondering whether CODESET_INCOMPATIBLE is one of thesse standard system exception (like INV_OBJREF). The form of the name suggest as such, however, I can't find any information on this matter anywhere. Any Codeset negotiation experts care to comment? Juergen, this is primarily an interop issue (since Chapter 13 is where this piece of wisdom about CODESET_INCOMPATIBLE appears), but with residual impact on language mappings and on Core Chapter 3 possibly. Jishnu. -- Jishnu Mukerji Systems Architect Email: jis@fpk.hp.com Hewlett-Packard EIAL, Tel: +1 973 443 7528 300 Campus Drive, 2E-62, Fax: +1 973 443 7422 Florham Park, NJ 07932, USA. Date: Wed, 21 Apr 1999 14:26:39 PDT Sender: Bill Janssen From: Bill Janssen To: interop@omg.org, Jishnu Mukerji Subject: Re: CODESET_INCOMPATIBLE exception CC: Uwe Seimet , cxx_revision@omg.org, issues@omg.org, orb_revision@omg.org References: <99Apr21.145641gmt-0100.27780@bam.bruker.de> <371DFA9E.7F643006@fpk.hp.com> Didn't we already go around on this one? Perhaps only in my head, or perhaps only on the Type Extensions DL -- or on a Type Extensions conference call. Yes, CODESET_INCOMPATIBLE was supposed to be one of the new system exceptions added by the Type Extensions submission. That makes it a Core issue, doesn't it? Bill Sender: jis@fpk.hp.com Date: Thu, 22 Apr 1999 11:19:02 -0400 From: Jishnu Mukerji Organization: Hewlett-Packard EIAL To: Bill Janssen CC: interop@omg.org, Uwe Seimet , cxx_revision@omg.org, issues@omg.org, orb_revision@omg.org Subject: Re: CODESET_INCOMPATIBLE exception References: <99Apr21.145641gmt-0100.27780@bam.bruker.de> <371DFA9E.7F643006@fpk.hp.com> <0r7Y_DkB0KGWF0rK8=@holmes.parc.xerox.com> Bill Janssen wrote: > > Didn't we already go around on this one? Perhaps only in my head, > or > perhaps only on the Type Extensions DL -- or on a Type Extensions > conference call. Yes, CODESET_INCOMPATIBLE was supposed to be one > of > the new system exceptions added by the Type Extensions submission. > That > makes it a Core issue, doesn't it? Thanks Bill. I am just trying to ensure that it is merely an editorial issue and not one that requires going through the whole vote in the RTF song and dance. All indications at present are that it is just an editorial issue. A piece of editing got dropped on the floor when the Type Extensions stuff was edited into the core, that needs to be picked up and placed where it belongs. Jishnu. -- Jishnu Mukerji Systems Architect Email: jis@fpk.hp.com Hewlett-Packard EIAL, Tel: +1 973 443 7528 300 Campus Drive, 2E-62, Fax: +1 973 443 7422 Florham Park, NJ 07932, USA.