I think we need a manifest with:
Permissions: sandbox
Codebase: java4k.com
I haven’t tried this yet.
Edit: I added them, but then got a slightly different warning message, when running from local disk (i.e. no webserver). Looks like running java applets direct from the file system is on its way out too.
Edit: So far I haven’t been able to remove the warning even using a webserver. I’m coming to the opinion that you can’t remove the warning, but if you don’t add the extra manifest entries, you java will refuse to run the applet outright on some future release. Edit: Actually I’m coming to the opinion that unsigned and self-signed won’t work at all next release whatever you do.
Edit: Oh and there is a warning on self-signed applications too. Looks like self-signing won’t work soon. I wonder whether installing my own self created root cert would fix that. I’m not sure whether that would work either, since java now phones home to check revocation lists. It might work provided security is not set to the highest setting.
Overall: If you buy a traceable code-signing certificate, you still get a warning the first time you run an applet, but I believe there is still a tick box to suppress it on future use. Unsigned and Self-signed applets work in this release, but display a warning every time and won’t work at all in a future release. I think this could be the last Java4k competition, as it will just about work this year, but won’t work at all next year, unless we go to traceable code signing, or have a custom downloader.