-
Key: I2JAV11-26
-
Legacy Issue Number: 4013
-
Status: closed
-
Source: hursley.ibm.com ( Simon Nash)
-
Summary:
The interop RTF resolved issue 3405 by adding a new service context called
ExceptionDetailMessage. The usage of this service context was
left to language mappings to define. We need to define this usage for Java.Writing the service context:
There are a few possibilities that come to mind:
1) The result of calling getMessage() on the exception.
2) The result of calling toString() on the exception.
3) The result of calling printStackTrace(PrintWriter) on the exception.I'm inclined to think that option 3 is best, since the callee's stack trace
is often very valuable debugging information.Reading the service context:
The wstring from the service context should become the Java error message
in the unmarshalled exception object. -
Reported: I2JAV 1.0 — Wed, 1 Nov 2000 05:00 GMT
-
Disposition: Resolved — I2JAV 1.1
-
Disposition Summary:
issue has been resolved, see ptc/01-10-20
-
Updated: Fri, 6 Mar 2015 20:58 GMT
I2JAV11 — Usage of ExceptionDetailMessage service context
- Key: I2JAV11-26
- OMG Task Force: IDL to Java December 2000 RTF