Note that even without changes in our build (to include new attributes in the manifest inside any jar files, and use the signed version of jars, etc) a workaround is to add http://pivot.apache.org in Site exception list under the Tab Security in the Java Control Panel (at least in Windows).
Finally, check if it makes sense now to use in Tutorials and Demos the unsigned version of our jars (and copy inside generated war files) ...
Note that the signing certificate that we use is self-signed so I'm not sure we could resolve this issue without some help from Infra. After some small local changes (but still not committed) Applets doesn't work because updated JRE 7 block them.
Some info here:
Test pages are available here (and served by the real http server):
After adding Pivot Web Site in Sites Exclusion List, all unsigned Applets restart to work (even without changes), so unless objections I'd make little changes but only in trunk (not under 2.0.x). But (self) signed Applets wont' work anymore the same (unless lowering a lot the Java Security bar I think).
As seen here:
required changes could be to add new properties for manifest in jars in build.xml, but keep the value of Permissions to sandbox, and for Codebase to empty string in build.properties .
And update generated applet properties to add something like this:
parameters.permissions = "sandbox";
in generated html pages for the web site and our war files.