Re: Do classes implementing Remote interfaces need to be Serializable?

Bob Scheifler wrote:
>> The UnicastRemoteObject details cause "stub replacement" to occur for any
>> attempt to serialize the UnicastRemoteObject.  The result is that noone
>> ever sees the object, but instead receives the remote proxy
>> implementation.
>
>
> Careful with your wording.  Automatic stub replacement will occur for
> any attempt to marshal the remote object in a JRMP call or into a
> MarshalledObject.  It does not occur during plain serialization,
> and does not occur over some other RMI implementations (IIOP, JERI).

Okay, thanks for clarifying that issue, I was, again, misremembering details.  I
was thinking about the JERI recommended work around of using writeReplace(),
which makes it happen for every case.

Gregg Wonderly

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html