-
Key: JAV2I14-2
-
Legacy Issue Number: 7595
-
Status: open
-
Source: Oracle ( Andrew Piper)
-
Summary:
Java serialization supports the serialization of proxy classes explicitly. It does this by essentially marshaling into the stream the list of interfaces that the proxy implements and on the other end calling Proxy.getProxyClass() with those interfaces. In RMI-IIOP the proxy class ends up coming across the wire with a repository ID of RMI:\U0024Proxy0:2D4A76C198E9D8DA:0000000000000000 (i.e. $Proxy) which is not a real class and cannot be loaded by the client.
I think we probably need to mandate specific behaviour for proxy classes along the lines of the java serialization spec. A simple approach might be to mandate that the valuetype contain a list of repids, the first being the pseudo-repid for the proxy itself and the other being the repids of the interfaces the proxy supports. The actual data would be that of the proxy itself which is basically the InvocationHandler.
-
Reported: JAV2I 1.2 — Tue, 20 Jul 2004 04:00 GMT
-
Updated: Wed, 11 Mar 2015 11:15 GMT
JAV2I14 — No wire format defined for java.lang.reflect.Proxy classes
- Key: JAV2I14-2
- OMG Task Force: Java to IDL 2005 RTF