org/omg/IOP/ExceptionDetailMessage.java .
Generated by the IDL-to-Java compiler (portable), version "3.2"
from /scratch/opt/mach5/mesos/work_dir/slaves/5af44a71-976a-41b7-81de-5773b84ec572-S39643/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/a3f74ad9-294f-4385-b9cc-31da721d8f41/runs/504babbb-611e-4037-9ed3-2563bc56551c/workspace/corba/src/java.corba/share/classes/org/omg/PortableInterceptor/IOP.idl
Tuesday, December 19, 2017 6:09:04 PM PST
CORBA formal/02-06-01: 13.7.1:
ExceptionDetailMessage identifies a CDR encapsulation of a wstring,
encoded using GIOP 1.2 with a TCS-W of UTF-16.
Field Detail
value
static final int value
CORBA formal/02-06-01: 13.7.1:
ExceptionDetailMessage identifies a CDR encapsulation of a wstring,
encoded using GIOP 1.2 with a TCS-W of UTF-16. This service context
may be sent on Reply messages with a reply_status of SYSTEM_EXCEPTION
or USER_EXCEPTION. The usage of this service context is defined
by language mappings.
IDL/Java: ptc/02-01-22: 1.15.2:
When a System Exception is marshaled, its GIOP Reply message shall
include an associated ExceptionDetailMessage service context. The
callee's stack trace is often very valuable debugging information but
may contain sensitive or unwanted information. The wstring within the
service context will therefore contain additional information relating
to the exception, for example the result of calling either
printStackTrace(PrintWriter) or getMessage() on the exception. When
unmarshaling a System Exception on the client side, the wstring from
any ExceptionDetailMessage service context shall become the Java error
message in the unmarshaled exception object.