WHAT HAPPENS IF YOU DOWNLAOD JAVA 1.7 UPDATE
WHAT HAPPENS IF YOU DOWNLAOD JAVA 1.7 CODE

Synopsis: Using the family CLSID to trigger loading of an applet does not work with certain JRE family versions. When specifying the codebase, using the Caller-Allowable-Codebase attribute or the Deployment Rule Set, make sure to list the domain where the JavaScript/HTML is hosted. Use the Deployment Rule Set (DRS) to allow the app and HTML to run without a warning.(Self signed can cause the LiveConnect dialog to show already or add a manifest file that specifies the Caller-Allowable-Codebase attribute.) Put the JAR files (or class files) and the HTML/JavaScript on the same host.You can work around this using one of the following approaches:

WHAT HAPPENS IF YOU DOWNLAOD JAVA 1.7 CODE

If the portion of the codebase that specifies the protocol, host, and port, are not the same for the unsigned JAR file (or class files) as for the JavaScript or HTML, the code will fail without a mixed code dialog warning.

Synopsis: JavaScript-> Java (LiveConnect) call fails silently if JavaScript/HTML and unsigned JAR/class files comes from different codebase host.

WHAT HAPPENS IF YOU DOWNLAOD JAVA 1.7 UPDATE

For more information, see Oracle Critical Patch Update Advisory. This release contains fixes for security vulnerabilities. The property will be evaluated only once when the class is loaded and initialized. The new system property (a boolean) is provided so that the compatible behavior can be enabled. The (TimeZone) method has been changed to throw a SecurityException if the method is called by any code with which the security manager's checkPermission call denies PropertyPermission('user.timezone', 'write'). Starting from JDK 7u45, the following new processing limits are added to the JAXP FEATURE_SECURE_PROCESSING feature.ДЇor more information, see the new Processing Limits lesson in the JAXP Tutorial. See Restore Security Prompts under the Security section of the Java Control Panel. The next time an application is started, the security prompt for that application is shown. When asked to confirm the selection, click Restore All.

To show prompts that were previously hidden, click Restore Security Prompts. A trust decision occurs when the user has selected the Do not show this again option in a security prompt. Restore Security PromptsДЄ new button is available in the Java Control Panel (JCP) to clear previously remembered trust decisions. Note that the RIA can still be started in any of the above cases.Дevelopers can refer to JAR File Manifest Attributes for more information. If the attribute is not present or if the attribute and location do not match, then the location of the JNLP file or HTML page is displayed in the security prompt shown to the user. The JavaScript to Java (LiveConnect) security dialog prompt is shown once per Applet classLoader instance.ДЄpplication-Library-Allowable-Codebase: If the JNLP file or HTML page is in a different location than the JAR file, the Application-Library-Allowable-Codebase attribute identifies the locations from which your RIA can be expected to be started.

JAR is unsigned and JavaScript calls happens from the same domain as the JAR location.

JAR is signed by a trusted CA, has the Caller-Allowable-Codebase manifest entry and JavaScript runs on the domain that matches it.

JavaScript to Java calls will be allowed without any security dialog prompt only if: Starting with 7u45, application developers can specify new JAR manifest file attributes:ДЄpplication-Name: This attribute provides a secure title for your RIA.Д¬aller-Allowable-Codebase: This attribute specifies the codebase/locations from which JavaScript is allowed to call Applet classes. Protections Against Unauthorized Redistribution of Java Applications JDK for Linux ARMДЄ JDK for Linux ARM is also available in this release. JDK 7u45 release includes JavaFX version 2.2.45. This update release includes a blacklist entry for a standalone JavaFX installer. For more information, see JRE Expiration Date. After either condition is met (new release becoming available or expiration date reached), Java will provide additional warnings and reminders to users to update to the newer version. This JRE (version 7u45) will expire with the release of the next critical patch update, scheduled for January 14, 2014.ДЇor systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 7u45) on February 14, 2014. Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Third Party Bulletin. The JRE expires whenever a new release with security vulnerability fixes becomes available.

For more information about security baselines, see Deploying Java Applets With Family JRE Versions in Java Plug-in for Internet Explorer.

What happens if you downlaod java 1.7