As mentioned in link http://download.oracle.com/javase/6/docs/technotes/guides/jweb/mixed_code.html For applications and applets that are designed to allow unsigned components, the
Trusted-Library attribute should be used. No warning dialog will be displayed and an application or applet may load jar files containing untrusted classes or resources.
But with the the latest jre 1.7 u45 we are getting security warning prompts. It is recommednded that newer Caller-Allowable-Codebase attribute should be used to handle the warning prompt. However, if I used newer one it will break the in updated 40 , and if I am using both display prompt will continue to come in jre 1.7 u45
Is there any solution to above problem? How can we support backward compatibility? In what sequence can we use the attribute such that both jre 1.7 u40 and 45 should stop display warning message?