Thierry, We give our applets all permissions. We are only using applets because it gives us ready access to web browser facilities, with the additional benefit of centralising the code base.
I suspect Batik may be doing something funny with the class loader. Applets are special when it comes to class loading, as all loading must be done by the applet class loader provided by the browser. Any guesses on the tooltip problem in my other email? Thanks Gavin Walker [EMAIL PROTECTED] Computer Scientist CSIRO Mathematical and Information Sciences Internet Marketplaces GPO Box 664 tel: +61 2 6216 7030 CANBERRA ACT 2601 AUSTRALIA fax: +61 2 6216 7111 -----Original Message----- From: Thierry Kormann [mailto:tkormann@;ilog.fr] Sent: Tuesday, 5 November 2002 8:49 PM To: Batik Users Subject: RE: Dynamic batik in applet > We have been using Batik in a signed applet and using simple > scripting in the svg document. This was satisfactory under > Batik 1.1.1. Under 1.5 things fall over. Our code can be run > as an applet or application and essentially does: > This works fine as an application. As an applet we get an exception under > plugin 1.3.1 and 1.4.1_01 (1.4.0 just used to hang the thread). Any help > with what is going on here? js.jar, which contains NativeScript, > is in the > applet classpath (ARCHIVE_VALUE or JAVA_ARCHIVE). looks like a security issue. Vincent is the right guy for that. Don't you have a way to turn security on/off through APIs ? Thierry. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
