See bug 4615605 for extra information.

java.lang.Throwable evolved in J2SE 1.4 to add a stack trace and a cause Throwable.  While 4615605 fixed interop between 1.3.1_04 and Hopper in the sense that Hopper will now receive the correct exceptions (and vice versa), the detailMessage is getting lost -- it gets set to null.  Unfortunately, this means that the toString method of Throwable in 1.3.1_04 generates NullPointerExceptions.

The problem comes from two issues with the ValueHandler:

1.  On the 1.3.1_04 side, the switch statements for reading class data based on FVD typecodes do not have tk_value.  They only have tk_value_box.

2.  On the Hopper side, the UnknownExceptionInfo service context is being encoded with GIOP 1.2 CDR even though 1.3.1_04 can only speak 1.0 CDR.

NOTE:  The fix for 4615605 did not cause these problems.  They were there, behind the problems addressed in 4615605.  The test case didn't print the exceptions, so didn't detect the error.

Expanded test case attached.

N/A

See evaluation in the description section.

Note again that this problem was not caused by the 1.3.1_04 fixes.  Even if these changes cannot go into 1.3.1_04, 1.3.1_04 is an improvement over 1.3.1_01.

Please see the webrevs at

http://javaweb.sfbay.sun.com/~eea1/eea1_patch2

The above are the necessary fixes for 1.3.1_04.

I will provide the webrevs for the necessary changes to Hopper (plus the above changes) shortly.

  xxxxx@xxxxx   2002-04-28