-
Bug
-
Resolution: Fixed
-
P2
-
1.4.0
-
03
-
generic
-
generic
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2056634 | 1.4.1 | Hemanth Puttaswamy | P2 | Closed | Fixed | rc |
A problem with javax.rmi.CORBA.Stub was identified several months ago. Since a protected default constructor was removed in JDK 1.4.0, the class's serialVersionUID changed.
For RMI-IIOP this wasn't a problem since it isn't used, but for Java Object Serialization or RMI-JRMP, it creates an incompatibility.
Usually, users write a stringified IOR to a file. However, it is allowed to use a java.io.ObjectOutputStream to write a Stub instance.
This was raised as an OMG issue 5332 in the Java to IDL RTF, and the vote recently passed, allowing us to include the legacy serialVersionUID in JDK 1.4.0 and beyond.
Please see
http://cgi.omg.org/issues/java2idl-rtf.html#Issue5332
Also see the Comments section.
For RMI-IIOP this wasn't a problem since it isn't used, but for Java Object Serialization or RMI-JRMP, it creates an incompatibility.
Usually, users write a stringified IOR to a file. However, it is allowed to use a java.io.ObjectOutputStream to write a Stub instance.
This was raised as an OMG issue 5332 in the Java to IDL RTF, and the vote recently passed, allowing us to include the legacy serialVersionUID in JDK 1.4.0 and beyond.
Please see
http://cgi.omg.org/issues/java2idl-rtf.html#Issue5332
Also see the Comments section.
- backported by
-
JDK-2056634 javax.rmi.CORBA.Stub incompatible between JDK 1.3.x and 1.4.x
- Closed