Issue 3633: Request clarification for use of alias typecodes in typedef helper classes (java-rtf)
Source:  (, )
Nature: Clarification
Severity: 
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?

Resolution: close no change
Revised Text: 
Actions taken:
May 19, 2000: received issue
April 28, 2003: closed issue
Discussion: 
Either approach appears to be valid, especially since the typecode equality semantics simply unwind tk_alias typecodes until they reach a non-tk_alias typecode. I think no change is needed here
End of Annotations:=====
Sender: bill
Message-ID: <39259654.5DC5ADAA@noise.force9.net>
Date: Fri, 19 May 2000 20:30:28 +0100
From: Bill <bill@noise.force9.net>
Reply-To: bill@noise.force9.net
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: issues@omg.org
Subject: IDL to Java mapping: Request clarification for use of alias
typecodes in 
 typedef helper classes
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: HIdd9G$6!!J<Be9pcp!!

Hi,

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?

cheers

Bill Hally