-
Key: I2JAV11-131
-
Legacy Issue Number: 3819
-
Status: closed
-
Source: Oracle ( Ken Cavanaugh)
-
Summary:
In the IDL to Java spec (ptc/00-01-08) there are several minor
editorial errors in the Java mapping for Typecode:1. p. 74 the example has
class TypeCode extends IDLEntity
However, IDLEntity is an interface, so this must be implements,
not extends.2. p. 75 the declaration
public abstract short member_visibility( long index )
should be
public abstract short member_visibility( int index )
since the IDL for member_visibility has a long argument,
and IDL long type maps to int in Java.3. Throughout class Typecode on pp. 74-75, TypeCodePackage.BadKind
and TypeCodePackage.Bounds are illegal java. The exception names
must either be fully qualified or unqualified with appropriate
import statements. -
Reported: I2JAV 1.0 — Fri, 8 Sep 2000 04:00 GMT
-
Disposition: Resolved — I2JAV 1.1
-
Disposition Summary:
closed issue...editorial
-
Updated: Fri, 6 Mar 2015 21:38 GMT
I2JAV11 — Issues with Java mapping of Typecode
- Key: I2JAV11-131
- OMG Task Force: IDL to Java December 2000 RTF