Issue 5728: How does a Java ORB implement a write_fixed/read_fixed? (java-rtf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: From the OMG mapping specs: 

org.omg.CORBA.portable.OutputStream [as of formal/01-06-06] defines: 

public void write_fixed(java.math.BigDecimal value, short digits, short scale) { 

throw new org.omg.CORBA.NO_IMPLEMENT(); 

} 

org.omg.CORBA.portable.OutputStream [as of formal/01-06-06] defines: 

public java.math.BigDecimal read_fixed(short digits, short scale) { 

throw new org.omg.CORBA.NO_IMPLEMENT(); 

} 

JDK 1.4 (and prior versions) do not implement the first two items, 
so no portable bindings could be used for these. 

Should there been an 
org.omg.CORBA_2_4.portable.OutputStream and org.omg.CORBA_2_4.portable.InputStream 
that inherit from org.omg.CORBA_2_3.portable.In/OutStream and add these? 


Resolution: Close no change
Revised Text: 
Actions taken:
October 28, 2002: received issue
April 28, 2003: closed issue
Discussion: 
Both the IDL to Java mapping specification and the .zip archive have the correct methods, so there is no OMG specification change required here. However, the two methods are indeed missing in J2SE 1.4, and so the originator of this issue should file a bug against the J2SE 1.4 CORBA implementation. (Wearing my Sun hat for a minute, I'll tell you that this error cannot be fixed until J2SE 1.5, since it requires adding new methods to a public interface). 

End of Annotations:=====
Subject: How does a Java ORB implement a write_fixed/read_fixed? 
Date: Mon, 28 Oct 2002 11:09:47 -0800 
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: How does a Java ORB implement a write_fixed/read_fixed? 
Thread-Index: AcJ+tZUU79WDmt9/STqqQBuYL9WIPQ== 
From: "George, David (Tandem)" <D.George@hp.com> 
To: <issues@omg.org> 
X-OriginalArrivalTime: 28 Oct 2002 19:09:47.0796 (UTC)
FILETIME=[953FC540:01C27EB5] 


From the OMG mapping specs: 

org.omg.CORBA.portable.OutputStream [as of formal/01-06-06] defines: 

public void write_fixed(java.math.BigDecimal value, short digits,
short scale) { 

throw new org.omg.CORBA.NO_IMPLEMENT(); 

} 

org.omg.CORBA.portable.OutputStream [as of formal/01-06-06] defines: 

public java.math.BigDecimal read_fixed(short digits, short scale) { 

throw new org.omg.CORBA.NO_IMPLEMENT(); 

} 

JDK 1.4 (and prior versions) do not implement the first two items, 
so no portable bindings could be used for these. 

Should there been an 
org.omg.CORBA_2_4.portable.OutputStream and
org.omg.CORBA_2_4.portable.InputStream 
that inherit from org.omg.CORBA_2_3.portable.In/OutStream and add
these? 

-dave. 


Issue 5728: Missing methods for fixed
-------------------------------------------------------------------------------------------


Summary: From the OMG mapping specs: 


org.omg.CORBA.portable.OutputStream [as of formal/01-06-06] defines: 


public void write_fixed(java.math.BigDecimal value, short digits,
short scale) { 


throw new org.omg.CORBA.NO_IMPLEMENT(); 


} 


org.omg.CORBA.portable.OutputStream [as of formal/01-06-06] defines: 


public java.math.BigDecimal read_fixed(short digits, short scale) { 


throw new org.omg.CORBA.NO_IMPLEMENT(); 


} 


JDK 1.4 (and prior versions) do not implement the first two items, 
so no portable bindings could be used for these. 


Should there been an 
org.omg.CORBA_2_4.portable.OutputStream and
org.omg.CORBA_2_4.portable.InputStream 
that inherit from org.omg.CORBA_2_3.portable.In/OutStream and add
these? 


Discussion:


Both the IDL to Java mapping specification and the .zip archive have
the correct
methods, so there is no OMG specification change required here.
However, the two
methods are indeed missing in J2SE 1.4, and so the originator of this
issue should
file a bug against the J2SE 1.4 CORBA implementation. (Wearing my Sun
hat for a minute,
I'll tell you that this error cannot be fixed until J2SE 1.5, since it
requires adding
new methods to a public interface).


Proposed Resolution: close no change.