CORBA24 — Transferring Java exception reason string across the wire

Although this is a Java-specific issue, I suspect it will have to be
decided in interop, therefore I'd like this to be an interop issue. I've
cc'ed java-rtf since I'm sure they'll be interested.

System exceptions only have: minor code, completion status. Java
exceptions all have a reason string as well. This is a potentially
significant bit of info that is not getting transferred across the wire in
Java ORB implementations. Our rmi over iiop customers expect this
information.

Our suggested solution is to create another service context for a system
exception reason string. When a system exception occurs, on a Java server,
the ORB places the reason string into this service context on the reply
message. On a Java client, the ORB checks for and extracts this string and
uses it when creating the system exception instance which is propagated to
the application code. If the service context doesn't exist, the Java ORB
just does what it does today. Any other client bindings may ignore this
service context.

Java bindings do not need to change for this proposal.

To be more precise (sorta), we need three things:
1. A new service context ID

const ServiceId SystemExceptionReason = TBD;

2. The context data associated with this ID is a CDR encapsulation of a
string.
3. Some verbage somewhere describing this.

closed/resolved