Legacy Issue Number: 2819
Summary: An issue we"ve run across is enumerating the set of system exceptions
that are valid to be passed via GIOP 1.0 (and similarly for 1.1, and
1.2). This is important for implementations of GIOP, which are, for
instance, attempting to map wire exceptions to C++ exceptions, and is
also important for packet-sniffing implementations.
Since many conforming GIOP 1.0 implementations were built (and bought)
and incorporated into products before various CORBA system exceptions
were added to the Core, it seems that servers should not raise `newer"
exceptions back to older clients – that is, clients speaking GIOP 1.0.
Instead, they should map those `newer" exceptions to UNKNOWN, I"d guess.
Reported: CORBA 2.3 — Wed, 21 Jul 1999 04:00 GMT
Disposition: Resolved — CORBA 2.4
closed in interop/2000-01-01
Updated: Fri, 6 Mar 2015 20:58 GMT