I'm developing a Java applet that requires some user feedback (the user opens a file chooser and selects files from the local system). I understand that the applet will need to be signed long term, but while I'm developing it, how can I get around the Java security model? As it is now, I get "access denied" errors when the user attempts to open the file chooser. Do I have to sign my applet every time I recompile it? If so, that's going to make testing a nightmare!
I'm fairly new to applet development, so I may be missing something obvious. But how do developers typically get around the security policies to actually test their code? There's got to be a way to do it, right?
I'm fairly new to applet development, so I may be missing something obvious. But how do developers typically get around the security policies to actually test their code? There's got to be a way to do it, right?
Facebook
Twitter