-
Key: I2JAV12-10
-
Legacy Issue Number: 4710
-
Status: closed
-
Source: International Business Machines ( Ann Collins)
-
Summary:
Sections 1.4.3 and 1.4.5 of the IDL to Java spec state that
character and string range and bounds checking should be performed
at marshal time. Since it is possible to receive IDL characters,
e.g UTF16 surrogate pairs, that cannot, at present, be mapped to
Java characters, could we clarify that this checking should be
performed at both marshaling and demarshaling time, per section
4.11.3.25 DATA_CONVERSION of the CORBA 2.5 spec which states:-
This exception is raised if an ORB cannot convert the
representation of data as marshaled into its native
representation or vice-versa.Also, could anyone please comment on the meaning of the term
"character set" in the sentence beginning "If the char falls
outside the range defined by the character set,..." in section
1.4.3. Does this refer to the TCS, NCS or both? -
Reported: I2JAV 1.1 — Wed, 21 Nov 2001 05:00 GMT
-
Disposition: Resolved — I2JAV 1.2
-
Disposition Summary:
Incorporate changes and close issue
-
Updated: Fri, 6 Mar 2015 20:58 GMT
I2JAV12 — Mapping for Character and String Types
- Key: I2JAV12-10
- OMG Task Force: IDL to Java 2002 RTF