Yes, the problem is that when I upgraded to xerces 2.5.0 I didn't update all the appropriate places. This only effects you when you run from jar files I (and probably most people working from CVS) normally run from the class files (not that the jars shouldn't work I'm just explaining my lameness :).
I'll commit the fix tonight. BTW the policy files were machine generated originally using the policy tool but have long since gone under manual control.
George Armhold wrote:
Furthermore, I notice that if I softlink xerces_2_5_0.jar to xerces_2_3_0.jar, squiggle works just fine. It seems to be unwilling to load xerces_2_5_0.jar.
George Armhold wrote:
> I notice that xerces was recently upgraded to 2_5_0 from 2_3_0. I > also notice the following stanza in > resources/org/apache/batik/apps/svgbrowser/resources/svgbrowser.policy: > > > grant codeBase "${app.dev.base}/lib/xerces_2_3_0.jar" { > permission java.security.AllPermission; > }; > > > Is this important? The header of the file suggests that it is > automatically generated, but I can't tell how; it seems static in the > ant build module. Any clues appreciated, thanks.
--------------------------------------------------------------------- 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]
