Hi All,
"Helder Magalhães" <[EMAIL PROTECTED]> wrote on 06/30/2008
08:45:18 AM:
> > Setting:
> > "C:\Users\ %username%\.java.policy"
> > To:
> > grant {
> > permission java.security.AllPermission;
> > };
> > Allowed getURL to work OK on both IE and FF3.
> > This tells me: stop being lazy and properly sign your applet, EVEN IF
you
> > are only in the early development/learning stages.
>
> This seems OK for local development but not for a decent attempt to
> widely deploy a Batik-based applet, i.e., obligating users to make
> such configuration is 1) bad for obvious security issues 2) less
> experienced users won't even able to do it.
Right, it's not good for general applet deployment.
> AFAIK, the main issue may be located in the sample applet's code
> itself - I recall Thomas Deweese has previously stated that the
> sand-boxing (which provokes this issue) resides in "setDocument" [1].
I doubt the problem is Batik's sandboxing. Unfortunately I
don't know what the source of the problem is. I think that getURL
should work in an Applet without needing signing. Can you get the
security exception that is causing the problem?
