N
Norris Watkins
I was wondering what will happen if the Objects passed as parameters to an
RMI call is modified by the server.
Since these objects are serialized/deserialized before the server code gets
access to the parameter objects, what the server views is only a copy of the
original object.
1. What prevents the server from calling modifiers on such objects ?
2. Will the answer for 1 above be different, if both server and client are
running under the same JVM ?
3. Is there a way in RMI to send the Class information along with the object
to the remote server ? ( So that the server does not have to have compile
time knowledge of the Class that it will handle at runtime )
4. Does JNDI use RMI ? ( If I do a lookup() for a particular object from a
client JVM, and if the object is sitting under a different JVM, how is that
the calls are being dispatched over the wire ? )
5. Can I bind() objects to JNDI, that are not implementing java.rmi.Remote
?
Thanks for reading
--nw
RMI call is modified by the server.
Since these objects are serialized/deserialized before the server code gets
access to the parameter objects, what the server views is only a copy of the
original object.
1. What prevents the server from calling modifiers on such objects ?
2. Will the answer for 1 above be different, if both server and client are
running under the same JVM ?
3. Is there a way in RMI to send the Class information along with the object
to the remote server ? ( So that the server does not have to have compile
time knowledge of the Class that it will handle at runtime )
4. Does JNDI use RMI ? ( If I do a lookup() for a particular object from a
client JVM, and if the object is sitting under a different JVM, how is that
the calls are being dispatched over the wire ? )
5. Can I bind() objects to JNDI, that are not implementing java.rmi.Remote
?
Thanks for reading
--nw