Issue 1256:  p.6.68 boxed values of complex types map to same type (obv-rtf)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: p.6.68: It is a bit awkward that boxed values of "complex" types map
 all to the same type (i.e., as for typedefs, the value"s name appears
 only in holder/helper classes), and that each boxed value of "basic" type
 maps to its individual class. Instead, boxed values of basic types
 could map to the corresponding java.lang.* class, e.g. 
 java.lang.Integer, java.lang.Short, etc. An issue with this approach 
 is that java.lang.Short and java.lang.Byte are not defined in JDK
 1.0.2. I doubt however this JDK is still much in use; for its users,
 short and octet could optionally map to e.g. CORBA.ShortValue and
 CORBA.ByteValue (inspired from CORBA::StringValue).
 
 

Resolution: 
Revised Text: 
Actions taken:
April 28, 1998: received issue
July 30, 1998: closed issue
Discussion: 

End of Annotations:=====
Issue 1256 (Eric Dujardin)
-------------------------
p.6.68: It is a bit awkward that boxed values of "complex" types map
all to the same type (i.e., as for typedefs, the value's name appears
only in holder/helper classes), and that each boxed value of "basic"
type
maps to its individual class. Instead, boxed values of basic types
could map to the corresponding java.lang.* class, e.g. 
java.lang.Integer, java.lang.Short, etc. An issue with this approach 
is that java.lang.Short and java.lang.Byte are not defined in JDK
1.0.2. I doubt however this JDK is still much in use; for its users,
short and octet could optionally map to e.g. CORBA.ShortValue and
CORBA.ByteValue (inspired from CORBA::StringValue).