Instances of user-defined classes not mapped to local class during replication

During replication, if an instance of a user-defined class is encountered,
the user-defined subclass is generated (if enableAutomaticClassGeneration
is set to true) or the error #rtErrClassDefNoClassForRemoteOop is raised.
No attempt is made to map a local class, even if it has the same name.

Workaround:

Define a replication specification in the remote object space that maps
the local class to the remote class name.