JAV2I12 — Descriptions of readAny and writeAny not precise enough

The descriptions of readAny and writeAny in section 1.5.1.4 of the Java to IDL
mapping spec are not very precise and don't say how null values should be handled.
These methods are currently described in section 1.5.1.4 as follows:

> The writeAny method writes the Java object obj to the output stream out in the
> form of a GIOP any. The readAny method reads a GIOP any from the input stream
> in and unmarshals it as a Java object, which is returned.

Proposed resolution:

Replace the above paragraph in section 1.5.1.4 by the following:

The writeAny method writes the Java object obj to the output stream out in the
form of a GIOP any. The contents of the GIOP any are determined by applying
the Java to IDL mapping rules to the actual runtime type of obj. If obj is null,
then it is written as follows: the TypeCode is tk_value, the repository ID is
"IDL:omg.org/CORBA/ValueBase:1.0", the name string is "", the ValueModifier is
VM_NONE, the concrete base is tk_null, the member count is 0, and the any's value
is a null valuetype (0x00000000).

The readAny method reads a GIOP any from the input stream in and unmarshals it
as a Java object, which is returned. The following TypeCodes are valid for
the GIOP any: tk_value, tk_value_box, and tk_objref. If the TypeCode is anything
other than these, a MARSHAL exception is thrown.

See revised text below.