-
Key: I2JAV11-21
-
Legacy Issue Number: 3633
-
Status: closed
-
Source: Anonymous
-
Summary:
I've noticed that there appears to be a lack of consistency between ORB vendors
when it comes to the use of alias typecodes in Java helper classes generated for
IDL typedefs.Specifically, both Visibroker 4 and Orbix 2000 return an appropriate alias
typecode from the helper class's type () method. However, the Visibroker 4
generated helper class does not use it in either the insert or extract methods,
whilst the Orbix 2000 helper class uses it to set the typecode of the Any passed
to the insert method and to check that the Any passed to the extract method is
of the correct type.Would it be possible to clarify which of these approaches is correct? From the
specification of the IDL to Java mapping, it appears that typdef types are
intended to be 'unwound' to the first non-typedef type, which would suggest that
the first approach is OK. However, if this is the case, for what purpose is the
alias typecode produced, if not for the setting/checking of typecodes of Anys
containing instances of the associated type? -
Reported: I2JAV 1.0 — Fri, 19 May 2000 04:00 GMT
-
Disposition: Resolved — I2JAV 1.1
-
Disposition Summary:
close no change
-
Updated: Fri, 6 Mar 2015 20:58 GMT
I2JAV11 — Request clarification for use of alias typecodes in typedef helper classes
- Key: I2JAV11-21
- OMG Task Force: IDL to Java December 2000 RTF