-
Key: JAV2I14-11
-
Legacy Issue Number: 2552
-
Status: closed
-
Source: Anonymous
-
Summary:
Summary: We should consider whether a Java class that has a writeReplace or a
readResolve method (with the appropriate signature for use by object
serialization) should map to a custom valuetype in IDL instead of
a normal valuetype. We should also think harder about the impact
of writeReplace/readResolve semantics on non-Java ORBs: can non-Java
implementations properly receive and send instances of such classes,
maintaining all the proper sharing, without running into type checking
problems, and without any additions to non-Java ORBs? -
Reported: JAV2I 1.0b1 — Fri, 19 Mar 1999 05:00 GMT
-
Disposition: Resolved — JAV2I 1.4
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
JAV2I14 — Treatment of classes with writeReplace/readResolve methods
- Key: JAV2I14-11
- OMG Task Force: Java to IDL 2005 RTF