Peter,
I'm still trying to grasp what you want to achieve...
Is it simply in-band code downloading?
Regards,
--
Michał Kłeczek
XPro Sp. z o. o.
ul. Borowskiego 2
03-475 Warszawa
PolskaBEGIN:VCARD
ADR;TYPE=pref;TYPE=work:;;ul. Borowskiego 2;Warszawa;;03-475;Poland
EMAIL:michal.klec...@xpro.biz
To enable remote clients to invoke processing at the server with lambda
expression invocation on remote objects, without code downloads.
Presently the enclosing class is serialized along with the lambda,
because it contains the receipe generated by the static compiler. I'm
investigating if
All you have to provide in the client is a class loading implementation that
knows about Util and pins it into a parent class loader from the class loaders
that proxies load. I netbeans, this happens because meta data declares that
such a relationship exists. In OSGi, this happens because
The whole point of my example is that the client has no knowledge of Util
interface - it is simply not interested in it.
The problem is not that the client cannot plug-in RMIClassProvider
dynamically. It is just that with current format of codebase annotation the
client cannot do anything. It
I'm open to suggestion.
Regards,
Peter.
- Original message -
Peter,
Can your SerialReflectionFactory expose an API to interact with the
stream? It would be enough to be able to retrieve context Collection
from ObjectStreamContext.
Thanks,
--
Michał Kłeczek
XPro Sp. z
Actually Lambda serialization is a good effort, I think we can leverage it by
removing the dependency on the enclosing class, but only for short lived
objects intended as arguments for remote objects.
ASM could be used to capture invokedynamic instructions used by the jvm to
create lambdas,
