I see. But why does it try to find org.apache.batik.swing.resources.Messages.class when this class is not even in the archive? There is a org.apache.batik.swing.Messages however.
Yes, except these files really should be able to be localized. The Messages*.properties files store all the UI text, see, java.util.ResourceBundle.
And if i set the locale on the canvas to English, why does it still try to retrieve the OS locale message properties (ie german)?
It appears that there isn't a clean way to avoid this given the design of Applets. What you really want to say is only check the contents of the Archives (jar files). But an applet always has 'codebase' on the class path - so it will always attempt to load 'missing' files from the server (as opposed to simply aborting).
Agreed.
I just like to be a bit more in control of the applet communication that's all :) It's not really bad behaviour on the part of the batik applet.Why is it so bad for the Applet to request these classes? (the Server should respond fairly quickly with a 404).
Hope this is still somehow batik relevant :)
Regards Jorg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
