The transferred elements are written as string or null
. The elements are converted to strings by
calling:
Objects.toString(element, null);
public | Creates a new instance. |
public | RMIArrayListStringElementWrapper( Creates a new instance for an iterable. |
public | RMIArrayListStringElementWrapper( Constructs a new instance for an iterator. |
Users shouldn't instantiate this class manually, but leave that to the RMI runtime.
Users shouldn't instantiate this class manually, but leave that to the RMI runtime.
The remaining elements in the iterator are added to a new ArrayList, which will be transferred.
Users shouldn't instantiate this class manually, but leave that to the RMI runtime.
If RMIWrapper.resolveWrapped() returned this
then this method will be called when the wrapper instance
is serialized to an other endpoint. It is preferred to return a remote proxy to the previously wrapped object to
pass back to the original endpoint when reverse request is made. Returning this
from this method
will result in the serialization of this wrapper through RMI.
If RMIWrapper.resolveWrapped() did not return this
then this method can freely return
null
or throw exceptions (e.g. UnsupportedOperationException) because it will never be
called.
this
.The result of this method will be returned to the caller, or used during the RMI request.
Important aspect of writing objects using wrappers is that in this method if any of the object writing method is called, then the non customizable aspects of the serializable will not be applied to the object that is being wrapped.
E.g. If an RMIWrapper is defined for an object type T, then calling
RMIObjectOutput.writeRemoteObject(