Re: java.Security.AccessControlException when starting Batik-Squiggle

2003-03-03 Thread Jakob Ilves
Hello! Thomas E Deweese wrote: > > You might also try getting the source distribution and building it > from scratch (it's fairly easy to do as long as you have the JDK). I've tried this and I can now get Squiggle up and running. Thanks! Right now that's enough for me. I really wished I

RE: java.Security.AccessControlException when starting Batik-Squiggle

2003-02-24 Thread Thomas E Deweese
> "JI" == Jakob Ilves <[EMAIL PROTECTED]> writes: JI> Hello! I've read the FAQ and tried my best to search for an JI> answer on the mailing list. JI> I've downloaded Batik 1.5beta4b and unpacked it using jar.exe JI> (from Sun JDK 1.4.0_02). When I try to start the program using JI> java -j

RE: java.Security.AccessControlException when starting Batik-Squiggle

2003-02-21 Thread Jansen Ward
s to local resources. Jan -Ursprüngliche Nachricht- Von: Gerard BUNEL [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 21. Februar 2003 15:04 An: Batik Users Betreff: Re: java.Security.AccessControlException when starting Batik-Squiggle Which is normal as extension jar files must be signed Ge

Re: java.Security.AccessControlException when starting Batik-Squiggle

2003-02-21 Thread Gerard BUNEL
Which is normal as extension jar files must be signed Gerard BUNEL "G. Wade Johnson" a écrit : > I had a similar problem recently that was caused by putting the batik library > files in the JRE extension directory. I could solve it by either removing the > library files from that directory or by

Re: java.Security.AccessControlException when starting Batik-Squiggle

2003-02-21 Thread G. Wade Johnson
I had a similar problem recently that was caused by putting the batik library files in the JRE extension directory. I could solve it by either removing the library files from that directory or by putting the squiggle jar file in the directory. Check the mailing list archives for a message from me