Subj : Re: Rhino and MS JVM (sic)
To   : Ariel Malka <ariel_ml@netvision.net.il>
From : Igor Bukanov <igor@fastmail.fm>
Date : Wed Aug 27 2003 09:40 am

Ariel Malka wrote:
>  ...
> Now, the exceptions i'm mentioning are not related to javascript
> evaluation errors.
> 
> They rather occur anytime Context.enter() and
> Context.initStandardObjects() are invoked.
> 
> But again, these are not fatal exceptions (javascript is being
> evaluated correctly).

Rhino uses reflection and query system properties to check for presence 
of optional features or post-JDK 1.1 classes. All such places are 
wrapped inside try { } catch(SecurityException ex) {} since 
SecurityException can be thrown in such cases under when Rhino runs 
inside an applet sandbox. The catch code for SecurityException never 
prints an exception stack trace and simply treat the exception as 
indication that the feature is not available. But it seems that MSJVM 
always prints stack trace for  com.ms.security.SecurityExceptionEx 
whenever it is thrown and Rhino has no control over it. Perhaps there 
are some registry settings to disable that automatic printout?..

But what you can do is to call initStandardObjects once during applet 
initialization and then use the scope objects it returns during script 
evaluation. In this way you will see the exceptions only once.

Regards, Igor

.