river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Kleczek <michal.klec...@xpro.biz>
Subject Re: Towards Internet Jini Services (trust)
Date Fri, 08 Oct 2010 14:30:30 GMT
On Thursday 07 of October 2010 21:57:48 Michal Kleczek wrote:
> 8. Before all this is implemented in PreferredClassProvider we have to
> cache association between a ClassLoader and a Module. It's implemented in
> RmiModule.
> 9. If we implement it in PreferredClassProvider our ClassLoaders can keep a
> reference to associated Module
> 10. If we implement it in PreferredClassProvider we can have different
> ClassLoaders for the same annotation but different ModuleAuthority - that
> would actually allow us to grant permissions to Modules - before that two
> different Modules with the same annotation are going to share permissions.

I think a hack to actually force a different ClassLoader for each unique 
RmiModule is to simply append a "dummy" randomly generated URL to the codebase 
annotation when loading classes using RMIClassLoader.


View raw message