| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2041326 | 1.4.0 | Everett Anderson | P3 | Closed | Won't Fix |
Though the new fixes for PutField/GetField allow a class to maintain compatibility with one older version with the same fields, they didn't
go far enough to allow the RMI-IIOP PutField/GetField mechanism to
ensure backwards compatibility when adding new fields.
The remote fields must be used in this case.
The attached test case provides an example of class evolution using
this mechanism. Try a client from the default and a server from the
putfields subdirectories, etc.
Use Rules.se to run against se or modify the Rules to use a rip-int build.
go far enough to allow the RMI-IIOP PutField/GetField mechanism to
ensure backwards compatibility when adding new fields.
The remote fields must be used in this case.
The attached test case provides an example of class evolution using
this mechanism. Try a client from the default and a server from the
putfields subdirectories, etc.
Use Rules.se to run against se or modify the Rules to use a rip-int build.
- backported by
-
JDK-2041326 Class evolution with PutField/GetField broken
-
- Closed
-
- relates to
-
JDK-4407244 RMI-IIOP's putFields/getFields implementation is broken
-
- Closed
-