>>>>> "GW" == Gavin Walker <[EMAIL PROTECTED]> writes:
GW> We give our applets all permissions. We are only using applets
GW> because it gives us ready access to web browser facilities, with
GW> the additional benefit of centralising the code base.
GW> I suspect Batik may be doing something funny with the class
GW> loader. Applets are special when it comes to class loading, as
GW> all loading must be done by the applet class loader provided by
GW> the browser.
I'm guessing we are setting up the JavaScript Interpreter in a
seperate ClassLoader (as permissions are most relyably granted/revoked
on a classloader basis), it is also possible that the problem is
fundamental with the rhino interpreter as I think it converts
javascript to java 'on the fly' - which probably means it creates it's
own class loader.
Sorry, no solution here, just more (hopefuly useful) information.
GW> Any guesses on the tooltip problem in my other email?
I believe this is a bug in JDK 1.4.1. I suppose it's possible we
do something to tickle the bug, but to date JDK 1.4.1 has not worked
at all on my machine (it doesn't seem to understand my video card at
all - the problems I see are _much_ worse than just a tool-tip window
hanging around).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
