I2JAV11 — Stub handling of UnknownException

Problem summary:
Following resolution of issue 5465 in vote 4, Section 1.21.6.3
"Streaming Stub APIs" 3rd main bullet reads as follows:

• If the CORBA system exception org.omg.CORBA.portable.UnknownException
  is thrown, the stub does one of the following:
• Translates it to org.omg.CORBA.UNKNOWN
• Translates it to the nested exception taht the UnknownException
  contains.
• Passes it on directly to the user

In order to preserve RMI semantics ORBs implementing the RMI-IIOP
protocol
must always translate the UnknownException to the nested exception given
by UnknownException.originalEx.

I think there are problems with the new final paragraph
a. It's unclear whether the additional paragraph requires a change to
Stub code or to the ORB runtime.
b. It's undesirable, and unnecessary in this case, to differentiate
between ORBs which do and do not implement RMI. The rule can, and
should, be the same for all Java ORBs.
c. It is incorrect to mandate that any ORB must translate the
UnknownException to the nested exception because, as the nested
exception is defined as a Throwable, this isn't always possible.

Proposal:
I think it would be preferable to simply reword Section 1.21.6.3
"Streaming Stub APIs" 3rd main bullet, as follows:

• If the CORBA system exception org.omg.CORBA.portable.UnknownException
  is thrown, the stub translates it to the nested exception that the
  UnknownException contains, if possible. If this is not possible, the
  stub passes the UnknownException on directly to the user.

Incorporate change and close issue