Re: Dynamic batik in applet

[Vincent Hardy]

Hello Gavin,

[EMAIL PROTECTED] wrote:

Hi Vincent,
Doh! One liner!

Actually, the ClassLoader issue was not the only thing I had to fix for getting things to work under JavaWeb Start but the fixes went in earlier.

> Could have had a work around weeks ago. Thank

you for fixing it. At least I hope it's fixed. I now get a "Can't find resource for bundle" error (any chance of being able
to cut and paste off the error dialog in the future).

You can cut and paste the error if you select the details button: that shows a text area where you can copy the stack trace.

> We are using

<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 20000303 Stylable//EN"
"http://www.w3.org/TR/2000/03/WD-SVG-20000303/DTD/svg-20000303-stylable.dtd";


I noticed in the CVS log that you also made changes to the DTD.  Do
we need to change our DOCTYPE?

You are using a very old DOCTYPE. For SVG 1.0, you should use the same as in the Batik samples.

If you ever need a special DOCTYPE and do not want to go over the network to retrieve it, you can edit the resources/org/apache/batik/dom/svg/resources/dtdids.properties and enter your public ID and system ID.

  Thank you, shows the value of Bugzilla a suppose in letting us know
when things get fixed.

Bugzilla only notifies the person who enters the bug, anybody on the cc list (and I think the module owner). So when we are the module owner and the one to fix the bug, we sometimes do not enter a bug in Bugzilla....

Cheers,
Vincent.

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: Vincent Hardy [mailto:[EMAIL PROTECTED]]
Sent: Monday, 18 November 2002 11:54 PM
To: Batik Users
Subject: Re: Dynamic batik in applet


Hello Gavin,

You may be running into an issue I found when running Batik in Java Web Start so you may want to try with the latest CVS if you are using 1.5beta4b (from memory, I think I fixed something in RhinoClassLoader where there was no delegation to the parent class loader).

Otherwise, it is not obvious from the stack trace that you are indeed running into a security issue and you could make sure by turning on the security debug options :

-Djava.security.debug=access failure
or
-Djava.security.debug=all

This will tell you exactly what where you are getting a security error, if any.

Good luck,
Vincent.

---------------------------------------------------------------------
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]