Premature object replacement

[Bernhard Haumacher (haui at haumacher dot de)]

All objects that implement the remote interface are replaced to their corresponding stubs during a remote method invocation. This happens without distinction whether the remotely called method expects a parameter of interface or implementation type. With the utmost probability this leads to a type conflict after unmarshaling the parameter.

Evaluation

The same problem exists in RMI, too. Remote server objects can not be marshaled in a remote method invocation. This is a principal problem, because object replacement during the serialization process occurs independent of the expected type of the instance variable or parameter that holds the original object. There is no workaround or fix for this problem.

Test

uka.test.replace.Main [-server | -client]

See also

ticket:13

closed since 1.03d.