JDK-4898230 : DefaultWriteObject Flag is always true in RMI-IIOP data stream
  • Type: Bug
  • Component: other-libs
  • Sub-Component: corba:idl
  • Affected Version: 1.4.2
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_8
  • CPU: generic
  • Submitted: 2003-07-30
  • Updated: 2003-11-15
  • Resolved: 2004-12-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.2 04Fixed
Related Reports
Relates :  
Description
A customer has complained that the DefaultWriteObject Flag is not set correctly in RMI-IIOP data streams.

In the code of 
com.sun.corba.se.internal.io.IIOPOutputStream.invokeObjectWriter()
it says this:

	    // Write format version
	    writeByte(kFormatVersionOne);

	    // Write defaultWriteObject indicator
	    // - We write this as false, but may have to go back and
		undo this if it is later called

              // Changed to true since this is what will happen in most
		cases.  We still need
              // to go back and fix this at some point.
	    writeBoolean(true);

Which is incorrect and needs to be fixed.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_04 FIXED IN: 1.4.2_04 INTEGRATED IN: 1.4.2_04
2004-06-14

EVALUATION ###@###.### 2003-08-04 We do not have resources for interop testing, so we are not sure if this is a bug. However, on code inspection, it does appear that our code is probably incorrect. The person who was the expert on this code is no longer with Sun, so it is hard to say, with authority, if this is a problem. ###@###.### 2003-10-21 will fix in 1.4.2_03 patch because its escalated, according to Ken Cavanaugh this fix is not needed in newer release(tiger)
2003-10-21