On Wed, Sep 24, 2008 at 5:09 PM, Fredrik Alströmer <[EMAIL PROTECTED]> wrote:
> The use case is actually rather simple, consider a general purpose > RMI-implementation. If an RMI-proxy object (created by the RMI-bundle, > and an invocation handler from that bundle) is called, all parameters > are serialized (so far so good), passed over the wire to the remote > JVM, where the parameters are deserialized and passed on to the > 'actual' implementation. Now, I must use the classloader from the > bundle which issued the call, as the parameters are instances of > classes which (in general) are only known to that bundle (I am > assuming at this point that the remote server has an equivalent bundle > available, that is a separate issue). IIRC, RMI will use the classloader of RemoteObject being referenced in the call to deserialize everything. So, that should also work since the RemoteObject is a domain object with its Import visibility set. What am I missing from the picture? Unless you are after dynamic classloading, then you will need to consult Paremus or others who have figured that part out. Cheers Niclas
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
