my problem was probably different from yours in that I need to be in a position to load Java classes "later", classes, I don't know the package name of ... so that's why I don't want/cannot have the scope (ImporterTopLevel'd scope) to be sealed
Maybe the insertion of "Packages" as described by wolffiex does the trick for ALL classes later on, not sure - anyway, for me it's fine that my run scopes can load whatever they want, I just wanted to ensure that they do not store all their stuff somewhere in the hierarchy of parent scopes. cu Merten > dev-tech-js-engine-rhino mailing list > [email protected]https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino Thanks for the suggestion. I took a look at ImporterTopLevel but didn't really see how this helped, it just moved the problem to a different scope since if I sealed the importer scope I ended up with the same exception. The other thing is that ImporterTopLevel does a Context.initStandardObjects() which is an expensive operation which I only want to do once, in the shared sealed scope. I found the reply by wolffiex to solve the problem by forcing the shared scope to load the needed properties before it gets sealed. _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
