Thanks of your hints.
I got a headache after reading documentation of Jini... Maybe a complex issue requires complex solution, but I'm not sure that Jini's way of working is a natural way to do things.
The XML serialization felt much more better, but it do not fill a requirement of 100% compatibility either.
Right now I'm going to call "a time out" for myself and sit down for a while and but some more focus to find & descripe the problematic of compatibility.
By the way, have your never tested to compile new class at runtime? Requirements of the runtime class could be handled via Abstract- and Interface classes.
Just figuring that the data (object and methods) could be in XML-format something like this:
<networkObject home="123.123.123.123" port="4444">
<class name="Command" compilerArguments="...>
class Command {
...
...
...}
</class>
<class ...>
...
</class>
<host name="localhost" port="4445" class="Command" arg=...>
<result>
</result>
</host>
<host name="111.222.333.444" class=...>
<result>
</result>
</host>
...
</networkObject>
Oh
fuck, this starts to sound as awful as other ways...
Br,
Jorma