The Sky is NOT Falling, Your Java is Fine!
By Ken Walker-Oracle on Nov 14, 2013
We weathered the storm because programmers checked and double-checked all of their date codes and calculations, and tested (and re-tested) all of their programs to be sure we were ready.
Let's apply this lesson to a more modern seed of chaos. People are understandably concerned that after the latest release of the Java Runtime Environment (Java(TM) Platform SE 7 U45), they may have seen some errors or warnings that appear to be a little bit, well; "alarming." On one hand, they're running an Oracle Product that they've known and loved for years (for example's sake, let's call it, "OTB" for "Oracle Teddy Bear"). On the other hand, they've recently been asked to upgrade a different Oracle product (the new Java JRE), and when they do, their beloved old OTB spits the following error out at them:
The JRE warns that, "This application will be blocked in a future Java security update because the JAR file manifest does not contain the Permissions attribute. Please contact the Publisher for more information."
Does this mean that OTB will be blocked and will fail to run if you upgrade to a new version of Java in the future?
The simple fact is, Oracle Developers do talk to one another and they are, as we speak, preparing future releases of OTB (and other Oracle product favorites) to work with new versions of Java like a well oiled machine! The error message about the "application being blocked in a future release" is there to alert other independent product developers about changes in Java that will ultimately affect their product(s) if action is not taken on their part. If you continue to ensure that you are upgrading and maintaining current releases of your Java Runtime Environment, along with all of the products that rely on it, you shouldn't have anything to worry about.