Issue 1129: How to handle unexpected exceptions? (interop) Source: (, ) Nature: Revision Severity: Summary: Summary: If I invoke an operation and the result is an exception that is not defined as part of the operation"s definition, what should happen? It seems obvious that a different exception needs to be raised but which one? MARSHAL? Resolution: Clarify to Be consistent with behaviour for system exceptions. Raise UNKNOWN exception Revised Text: 15.3.5.5 change the last sentence to the following: " If an ORB receives a non-standard system exception that it does not support, or a user exception that is not defined as part of the operation's definition, the exception shall be mapped to UNKNOWN. " Actions taken: April 2, 1998: received issue July 13, 1998: moved from orb_revision to interop March 8, 1999: closed issue Discussion: End of Annotations:===== Return-Path: Sender: jon@floorboard.com Date: Thu, 02 Apr 1998 11:06:29 -0800 From: Jonathan Biggar To: issues@omg.org, orb_revision@omg.org Subject: How to handle unexpected exceptions? If I invoke an operation and the result is an exception that is not defined as part of the operation's definition, what should happen? It seems obvious that a different exception needs to be raised but which one? MARSHAL? -- Jon Biggar Floorboard Software jon@floorboard.com jon@biggar.org Return-Path: X-Authentication-Warning: tigger.dstc.edu.au: michi owned process doing -bs Date: Fri, 3 Apr 1998 05:59:18 +1000 (EST) From: Michi Henning To: Jonathan Biggar cc: issues@omg.org, orb_revision@omg.org Subject: Re: How to handle unexpected exceptions? On Thu, 2 Apr 1998, Jonathan Biggar wrote: > If I invoke an operation and the result is an exception that is not > defined as part of the operation's definition, what should happen? > It > seems obvious that a different exception needs to be raised but > which > one? MARSHAL? No - "impossible" user exceptions from an operation are translated to the UNKNOWN system exception. The spec mandates this somewhere, but sorry, I can't recall exactly where. Cheers, Michi. -- Michi Henning +61 7 33654310 DSTC Pty Ltd +61 7 33654311 (fax) University of Qld 4072 michi@dstc.edu.au AUSTRALIA http://www.dstc.edu.au/BDU/staff/michi-henning.html Return-Path: Sender: jon@floorboard.com Date: Thu, 02 Apr 1998 12:07:20 -0800 From: Jonathan Biggar To: Michi Henning CC: issues@omg.org, orb_revision@omg.org Subject: Re: How to handle unexpected exceptions? References: Michi Henning wrote: > > On Thu, 2 Apr 1998, Jonathan Biggar wrote: > > > If I invoke an operation and the result is an exception that is > not > > defined as part of the operation's definition, what should happen? > It > > seems obvious that a different exception needs to be raised but > which > > one? MARSHAL? > > No - "impossible" user exceptions from an operation are translated > to > the UNKNOWN system exception. The spec mandates this somewhere, but > sorry, > I can't recall exactly where. The Interop 1.2 RTF results state that an unknown system exception is mapped to UNKNOWN, but is silent about unknown user exceptions. -- Jon Biggar Floorboard Software jon@floorboard.com jon@biggar.org