Submitted On 04-AUG-2006
marco_nijdam
For us this is a show stopper. We can't use Java 5. Our application transfers CORBA structs in CORBA:Any objects. The repository ID is included in the Any. So client and server no longer interoperate since they use different reference IDs (unless run this Java 5 version, which they don't).
Submitted On 04-AUG-2006
Same as above, it's a show-stopper as I can no longer interoperate with non Java 5 CORBA code.
Submitted On 11-NOV-2006
jcedata
This bug does not seem to be fixed in Java 6 rc. Very strange considering the severity of the bug since it breaks Corba interoperability.
Submitted On 29-JAN-2007
I can confirm what jcedata says. This is not fixed in Java 6.
Submitted On 21-JUN-2007
sraza77
The problem has not been fixed in Java 6. What's the point of write-once run everywhere, if we can't get something as basic as interoperability between 1.4 CORBA Clients and 1.6 CORBA Servers.
Submitted On 04-MAR-2008
ericpierskalla
This is NOT fixed in the 1.6 JDK release 3, 4 or 5.
What are you people waiting for?
Submitted On 05-MAR-2008
ericpierskalla
Just tried this again using:
jdk1.6.0
jdk1.6.0_01
jdk1.6.0_02
jdk1.6.0_03
jdk1.6.0_04
jdk1.6.0_05
The same problem exists.
Submitted On 10-MAR-2008
coffeys
ericpierskalla,
as the bug report indicates - this fix is in 6u10 which is still a few months away from general release. If you need a fix in the interim and have a support contract please contact sun service to get the issue escalated.
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|