Hi, I am found the following solution to the problem: simply do not call the stopProcessing() method in the destroy() method of the applet... this is not clean, but it works, and does neither produce any exceptions nor any other side-effects. If I sign the applet, it works, too, but as this implies that Java computes a hash for every classfile in the Batik Jar archive when running the applet, this is not really performant. I could also just put the one class which causes the exception into a separate Jar file and only sign this, but that is imho less elegant than simply not calling stopProcessing(). Thanks for the help.
Regards, Chris -- Chris Cruzdal __________________________________ Do you Yahoo!? Yahoo! Search - Find what you’re looking for faster http://search.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
