Hi All, I seem to be having some strange problems with (I think?) classpath. I am running an OSGi framework with a JINI driver (encapsulating RMI methods), and have run into some (possible) inconsistencies between J2SE1.42 and jamvm/classpath0.9. To cut a long story short, as far as I can tell after starting the Jinidriver bundle, the service registrar is recieved. On Sun's implementation this works fine, i can then run all the jini services i want over RMI. Perfect. However, using classpath I get an accessControlException thrown with the error "no protection domains". I added a little bit of debug to sun's jini code, and just made it print out the result of getProtectionDomain just before the function i believe is failing to complete its doPrivelidged section. Under J2SE the calling class, classloader (of the OSGi framework) and all.permissions are reported. Under jamvm/classpath however, the classloader is report as null.... which i'm sure is not quite right. Has anyone had any experience with RMI/Jini under jamvm/classpath? In both cases, the RMISecurityManger is set to be in use. I should point out that the "server" offering the RMI service is running J2SE. As always , i'm right up against it, and my eyes are sore from looking through sourcecode of the possible source of the problem. If anyone can offer any suggestions/help/debugging advice/magic, I would appreciate it so much. Cheers in advance, Dave Bath -------------- next part -------------- An HTML attachment was scrubbed... URL: http://developer.classpath.org/pipermail/classpath/attachments/20060504/fcc024ef/attachment.html
