On Mar 11, 8:22 am, Norris Boyd <[EMAIL PROTECTED]> wrote: > On Mar 10, 10:15 pm, Zappie <[EMAIL PROTECTED]> wrote: > > Look at NativeJavaTopPackage.init, specifically the topNames variable.
Thank you very much, Norris. It's good to know I haven't completely lost my mind (well, that's subject to debate, but I digress...). Basically, if it's on the path, it is accessible to Packages (unless it's in the ClassShutter invisibility list, and I'm not even sure how to define one of those). I created a dummy standalone jar, fired up the Rhino debugger with the jar in my classpath, and I had no problems. So now the trick is getting the object on the Monkey classpath. My guess is that by registering a Monkey extension point for my Eclipse plug-in, that will force the object I return to be on the class path and thus load its related classes. I'm not 100% clear on that, but classloader issues have never been my strong suit. Okay, back to the laboratory, Igor... _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
