Legacy Issue Number: 4189
Source: IONA ( Mark Spruiell)
In document 01-01-01, there are the following paragraphs which seem
contrary to one another regarding the minor code to be used when an
ORB receives an unrecognized system exception.
Vendors may define non-standard system exceptions, but these exceptions are
discouraged because they are non-portable. A non-standard system exception, when
passed to an ORB that does not recognize it, shall be presented by that ORB as an
UNKNOWN standard system exception. The minor code and completion status from
the unrecognized exception shall be preserved in the UNKNOWN exception.
Exceptions are encoded as a string followed by exception members, if any. The string
contains the RepositoryId for the exception, as defined in the Interface Repository
chapter. Exception members (if any) are encoded in the same manner as a struct.
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, with standard minor code set to 2 for a system exception, or
set to 1 for a user exception.
Reported: CORBA 2.4.2 — Sat, 3 Feb 2001 05:00 GMT
Disposition: Resolved — CORBA 2.5
Incorporate changes and close issue
Updated: Fri, 6 Mar 2015 20:58 GMT