Jdk 7u45 linux x64

Update Release Notes

Java™ SE Development Kit 7, Update 45 (JDK 7u45)

The full version string for this update release is 1.7.0_45-b18 (where «b» means «build»). The version number is 7u45.

Highlights

Olson Data 2013d

JDK 7u45 contains Olson time zone data version 2013d. For more information, refer to Timezone Data Versions in the JRE Software.

Security Baselines

The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 7u45 are specified in the following table:

JRE Family Version	JRE Security Baseline (Full Version String)
7	1.7.0_45
6	1.6.0_65
5.0	1.5.0_55

JRE Expiration Date

The JRE expires whenever a new release with security vulnerability fixes becomes available. Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Third Party Bulletin. This JRE (version 7u45) will expire with the release of the next critical patch update, scheduled for January 14, 2014.

For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 7u45) on February 14, 2014. 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. For more information, see JRE Expiration Date.

Blacklist Entries

This update release includes a blacklist entry for a standalone JavaFX installer.

JavaFX Release Notes

JavaFX is now part of JDK. JDK 7u45 release includes JavaFX version 2.2.45.

JDK for Linux ARM

A JDK for Linux ARM is also available in this release.

New Features and Changes

Protections Against Unauthorized Redistribution of Java Applications

Starting with 7u45, application developers can specify new JAR manifest file attributes:

Application-Name : This attribute provides a secure title for your RIA.

Caller-Allowable-Codebase : This attribute specifies the codebase/locations from which JavaScript is allowed to call Applet classes.

JavaScript to Java calls will be allowed without any security dialog prompt only if:

• JAR is signed by a trusted CA, has the Caller-Allowable-Codebase manifest entry and JavaScript runs on the domain that matches it.
• JAR is unsigned and JavaScript calls happens from the same domain as the JAR location.

The JavaScript to Java (LiveConnect) security dialog prompt is shown once per Applet classLoader instance.

Application-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.

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.

Note that the RIA can still be started in any of the above cases.

Developers can refer to JAR File Manifest Attributes for more information.

Restore Security Prompts

A new button is available in the Java Control Panel (JCP) to clear previously remembered trust decisions. A trust decision occurs when the user has selected the Do not show this again option in a security prompt. To show prompts that were previously hidden, click Restore Security Prompts. When asked to confirm the selection, click Restore All. The next time an application is started, the security prompt for that application is shown.

See Restore Security Prompts under the Security section of the Java Control Panel.

JAXP Changes

Starting from JDK 7u45, the following new processing limits are added to the JAXP FEATURE_SECURE_PROCESSING feature.

• totalEntitySizeLimit
• maxGeneralEntitySizeLimit
• maxParameterEntitySizeLimit

For more information, see the new Processing Limits lesson in the JAXP Tutorial.

TimeZone.setDefault Change

The java.util.TimeZone.setDefault(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») . The new system property jdk.util.TimeZone.allowSetDefault (a boolean) is provided so that the compatible behavior can be enabled. The property will be evaluated only once when the java.util.TimeZone class is loaded and initialized.

Bug Fixes

This release contains fixes for security vulnerabilities. For more information, see Oracle Critical Patch Update Advisory.

Known Issues

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

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.

You can work around this using one of the following approaches:

• Put the JAR files (or class files) and the HTML/JavaScript on the same host.
• Sign the JAR files. (Self signed can cause the LiveConnect dialog to show already; or add a manifest file that specifies the Caller-Allowable-Codebase attribute.)
• Use the Deployment Rule Set (DRS) to allow the app and HTML to run without a warning.

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.

Area: Deployment/Plugin
Synopsis: Using the family CLSID to trigger loading of an applet does not work with certain JRE family versions.

If you use the family CLSID to trigger loading of an applet with a certain JRE family version, the family CLISD will be ignored and the latest JRE version installed on your system is used to load the applet instead. Family CLSID is specific to Internet Explorer. The workaround is to use the java_version applet parameter or the version attribute of the Java element in JNLP file instead.

Area: Deployment/Plugin
Synopsis: Certificate-based DRS rule does not work when main JAR is in nested resource block

The certificate-based Deployment Rule Set rule does not work properly for JNLP applications when the main JNLP file has no JAR files, or all JAR files are in nested resource blocks nested in or elements.

Area: Deployment/Plugin
Synopsis: Caller-Allowable-Codebase may be ignored when used with Trusted-Library .

If a trusted, signed JAR file is using the Caller-Allowable-Codebase manifest attribute along with Trusted-Library then the Caller-Allowable-Codebase manifest entry will be ignored and, as a result, a JavaScript -> Java call will show the native LiveConnect warning. The workaround is to remove the Trusted-Library manifest entry.

Area: Deployment/Plugin
Synopsis: Applet could fail to load by throwing NPE if pack compression is used with deployment caching disabled.

If a JAR file is using pack compression with manifest entries Permissions and Caller-Allowable-Codebase while deployment caching is disabled, then:

• The Permissions manifest entry will be ignored. (This can be seen from the fact that yellow warning is there on security dialog even though the Permissions attribute is there.) This only happens if Caller-Allowable-Codebase attribute is present along with the Permissions attribute.
• The Caller-Allowable-Codebase attribute will cause the applet to fail to load by throwing a java.lang.NullPointerException .

If you want to use pack compression with the Caller-Allowable-Codebase attribute, there are two possible workarounds:

• Enable caching and all issues listed will disappear.
• Do not use the pack property jnlp.packEnabled=true while deploying the applets using Caller-Allowable-Codebase and premissions property. Instead use the ContentType servlet for serving the pack files.

Area: Deployment/Plugin
Synopsis: Non-JNLP trusted applet fails to load using the file:\\ URL.

Local trusted applets that do not deploy using a JNLP file will fail to load by throwing a java.lang.NullPointerException . You can work around this issue by using one of the following methods:

• Use a JNLP file to launch the applet.
• Try loading the applet over HTTP or HTTPS.

Area: Deployment/Plugin
Synopsis: JNLP applet fails to load if using JNLP versioning.

Due to this bug, if you are using the jnlp.versionEnabled property for JAR versioning in your browser applet, your applet might not start. Also users might see a yellow warning about a missing Permissions attribute in the following two scenarios:

• The jnlp.versionEnabled property is set to false inside the JNLP file and the version is defined against the main JAR file.
• You use JNLPDownloadServlet for version download support.

The workaround is to either not use versioning via jnlp.versionEnabled , or to use the JNLPDownloadServlet servlet for version support instead.

Area:: client-libs/AWT
Synopsis: Using RMI from a restricted environment may cause a NullPointerException .

If an application uses RMI and runs in a restricted environment (ie. Java Plugin, Java Web Start), it may not work. In particular, if you run a UI from an RMI callback, a NullPointerException is likely to be thrown.

Источник

Java Archive

The Oracle Java Archive offers self-service download access to some of our historical Java releases

WARNING: These older versions of the JRE and JDK are provided to help developers debug issues in older systems. They are not updated with the latest security patches and are not recommended for use in production.

For production use Oracle recommends downloading the latest JDK and JRE versions and allowing auto-update.

Only developers and enterprise administrators should download these releases.

Downloading these releases requires an oracle.com account. If you don’t have an oracle.com account you can create one here.

For current Java releases, please visit Oracle Java SE Downloads.

Current update releases for JDK 7 is available for support customers.

For more information on the transition of products from the legacy Sun download system to the Oracle Technology Network, visit the SDLC Decommission page announcement.

Previous Java releases

Java SE

Java Client Technologies
Java 3D, Java Access Bridge, Java Accessibility, Java Advanced Imaging, Java Internationalization and Localization Toolkit, Java Look and Feel, Java Media Framework (JMF), Java Web Start (JAWS), JIMI SDK

Java Platform Technologies
Java Authentication and Authorization Service (JAAS), JavaBeans, Java Management Extension (JMX), Java Naming and Directory Interface, RMI over IIOP, Java Cryptography Extension (JCE), Java Secure Socket Extension

Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files
The Java Cryptography Extension enables applications to use stronger versions of cryptographic algorithms. JDK 9 and later offer the stronger cryptographic algorithms by default.

The unlimited policy files are required only for JDK 8, 7, and 6 updates earlier than 8u161, 7u171, and 6u181. On those versions and later, the stronger cryptographic algorithms are available by default.

Java Database
Java DB Connectivity (JDBC), Java Data Objects (JDO)

Misc. tools and libraries
Sample Code for GSSAPI/Kerberos, Java Communications API

Java SE downloads

Java EE

Java EE SDK
Java Application Platform SDK, Java EE SDK, Samples

GlassFish Server
GlassFish, Sun Java System Application Server, IDE Toolkit, Java Application Verification Kit (AVK) for Enterprise, Project Metro Web Services

Java EE Documentation
First Cup, Javadocs, Tutorials, Demos, Blueprints

Java EE Platform
J2EE Application Deployment, J2EE Client Provisioning, J2EE Connector Architecture, J2EE Deployment, J2EE Management, Java API for XML, Java Messaging Service (JMS), Java Servlet, Java Transaction Service (JTS), JavaMail, JavaServer Faces, Struts and Core J2EE

Java ME

DVB, J2ME Connected Limited Device Configuration (CLDC), J2ME Mobile Information Device Profile (MIDP), Java Card, Mobile Media API Emulator (MMAPI), Java ME SDK, Java TV, OCAP Sun Specification, Project Lightweight UI Toolkit, Security and Trust Services API for J2ME (SATSA), Wireless Toolkit, Documentation and Exclusion List Installer

Источник

Jdk 7u45 linux x64

Your search did not match any results.

We suggest you try the following to help find what you’re looking for:

• Check the spelling of your keyword search.
• Use synonyms for the keyword you typed, for example, try “application” instead of “software.”
• Try one of the popular searches shown below.
• Start a new search.

Java TM SE Development Kit 7 Update 80 and NetBeans TM IDE 8.0.2 Java SE Software Bundle Installation Instructions

The following instructions describe how to install the Java TM Platform, Standard Edition Development Kit (Java SE 7 Update 80 JDK TM ) and the NetBeans TM IDE 8.0.2 Java SE integrated development environment bundle.

Contents

The Software Bundle Distribution

The Java TM SE Development Kit 7 Update 80 and NetBeans TM IDE 8.0.2 Java SE Software Bundle is distributed for various platforms as follows:

Installation Filename	Platform
jdk-7u80-nb-8_0_2-windows-i586.exe	Windows x86 (32-bit)
jdk-7u80-nb-8_0_2-windows-x64.exe	Windows x64 (64-bit)
jdk-7u80-nb-8_0_2-linux-i586.sh	Linux x86 (32-bit)
jdk-7u80-nb-8_0_2-linux-x64.sh	Linux x64 (64-bit)
jdk-7u80-nb-8_0_2-macosx-x64.dmg	OS X v10.7.3 (64-bit)

Note: Java TM SE Development Kit 7 Update 80 cobundles JavaFX 2.2.

Installing the Software Bundle on Microsoft Windows

To install the software, you must have administrator privileges on your system. The installer places the Java Runtime Environment (JRE) software in %Program Files%\Java\jre7 , regardless of the specified JDK install location.

Note: This installer does not displace the system version of the Java platform that is supplied by the Windows operating system.

Before You Install

1. Verify that your system meets or exceeds the minimum hardware requirements:
   1. 800MHz Intel Pentium III or equivalent
   2. 512 MB of RAM.
   3. 750 MB of free space

   Note: The installer uses the %USERPROFILE%\Local Settings\Temp directory to store temporary files.

Verify that you have administrator privileges on your system.

Download the installer file and save it on your system.

1. For the 32-bit Windows operating system, the installer file name is jdk-7u80-nb-8_0_2-windows-i586.exe .
2. For the 64-bit Windows operating system, the installer file name is jdk-7u80-nb-8_0_2-windows-x64.exe .

Installing the Software

1. Double-click the installer file to run the installer.
2. At the Welcome page of the installation wizard, click Next.
3. At the JUnit License Agreement page, decide if you want to install JUnit and click the appropriate option, click Next.
4. At the JDK Installation page, specify which directory to install the JDK into and click Next.
5. At the NetBeans IDE Installation page, do the following:
   1. Specify the directory for the NetBeans IDE installation.
   2. Accept the default JDK installation to use with the IDE or specify another JDK location.
6. Click Next.
7. Review the Summary page to ensure the software installation locations are correct.
8. Click Install to begin the installation.
9. At the Setup Complete page, provide anonymous usage data if desired, and click Finish.

   When the installation is complete, you can view the log file, which resides in the following directory: %USERPROFILE%\.nbi\log.

   Installing the Software Bundle on Linux

   You can install the JDK software and NetBeans IDE in directories of your choice. You do not have to be a root user to use this installer unless you choose to install this bundle in a system-wide location.

   Note: This installer does not displace the system version of the Java platform that is supplied by the operating system.

   Before you install

   1. Verify that your system meets or exceeds the recommended minimum hardware requirements:
      1. Pentium III workstation, 800 MHz
      2. 512 MB of RAM
      3. 700 MB of free space

      Note: The installer uses the /tmp or the /var/tmp directory for temporary files.

10. Download the installer file and save it on your system.
    1. For the 32-bit Linux operating system, the installer file name is jdk-7u80-nb-8_0_2-linux-i586.sh
    2. For the 64-bit Linux operating system, the installer file name is jdk-7u80-nb-8_0_2-linux-x64.sh
11. Navigate to the directory into which you downloaded the installer file and type:

    chmod +x to change the installer file’s permissions so it can be executed.

    Installing the Software

    Type the following command from the directory where you placed the installation file:

12. At the Welcome page of the installation wizard, click Next.
13. At the JUnit License Agreement page, decide if you want to install JUnit and click the appropriate option, click Next.
14. At the JDK Installation page, specify the directory where to install the JDK and click Next.
15. At the NetBeans IDE Installation page, do the following:
    1. Specify the directory for the NetBeans IDE installation.
    2. Accept the default JDK installation to use with the IDE or specify another JDK location.
16. Click Next.
17. Review the Summary page to ensure the software installation locations are correct.
18. Click Install to begin the installation.
19. At the Setup Complete page, provide anonymous usage data if desired, and click Finish.

    When the installation is complete, you can view the log file, which resides in the following directory:

    Note: If you choose to install this bundle into a system-wide location such as /usr/local , you must first login as root to gain the necessary permissions.

    Installing the Software Bundle on OS X

    The Software Bundle can be installed only on OS X v10.7.3 (Lion) or newer. The installer refuses earlier OS X releases.

    Note: This installer does not displace the system version of the Java platform that is supplied by the operating system.

    Before you install

    If you are installing on OS X, install the required OS X updates before proceeding further. If you install this bundle without having first installed the proper OS X updates, you may experience unexpected behavior with the installer or the Java platform.

    Note: You can check for the available updates at http://support.apple.com/downloads.

20. Verify that your system meets or exceeds the recommended minimum hardware requirements:
    1. Dual-Core Intel (64-bit)
    2. 1 GB of RAM
    3. 700 MB of free space
21. Download the jdk-7u80-nb-8_0_2-macosx-x64.dmg installer file.

Installing the Software

1. After the download completes, run the installer. The installer file has the .dmg extension.
2. On the panel that opens double-click the package icon. The package has the .mpkg extension. The installation wizard starts.
3. At the Introduction page of the installation wizard, click Continue.
4. At the Installation Type page, select the appropriate option below:
   1. To perform a standard installation of the Software Bundle, click Install.
   2. To specify another installation location, click Change Install Location.
5. (Optional, required if you clicked Change Install Location in step 4) At the Destination Select page, specify the disk for Software Bundle installation and click Continue.
6. (Optional, required if you clicked Change Install Location in step 4) At the Installation Type page, click Install.
7. Enter the administrator’s name and password for your system and click Install Software to begin the installation.

   The Installation page displays the progress of the installation.

8. When the installation is complete, click Close at the Summary page.

Uninstalling the Software from Windows

Each product in the bundle must be uninstalled separately.

To uninstall the IDE:

1. Shut down the IDE.
2. From the Control Panel, select Uninstall a program.
3. Select NetBeans IDE 8.0.2 and click Remove.

To uninstall the JDK and JavaFX 2.2:

1. From the Control Panel, select Uninstall a program.
2. Select Java(TM) SE Development Kit 7 Update 80 from the list and click Remove.

Note: If you uninstall the JDK, but want to continue using NetBeans IDE 8.0.2, you must set the IDE’s -jdkhome option to point to an another installation of the JDK as outlined below.

To uninstall the Java Runtime Environment:

1. From the Control Panel, select Uninstall a program.
2. Select Java 7 Update 80 from the list and click Remove.

To change the value of -jdkhome :

1. Navigate to the etc folder of the NetBeans IDE installation directory. The default location is C:\Program Files\NetBeans 8.0.2\etc .
2. Open the netbeans.conf file in a text editor and edit the netbeans_jdkhome option.

Note: Java TM SE Development Kit (JDK) 5.0 and JDK 6 are not supported on any platform for this release. You must have JDK 7 Update 10 (or newer) on your system to install and run NetBeans IDE 8.0.2.

Uninstalling the Software from Linux

Each product in the bundle must be uninstalled separately.

To uninstall the IDE:

1. Navigate to the installation directory of the NetBeans IDE.
2. Type ./uninstall.sh to run the uninstaller.

To uninstall the JDK and JavaFX 2.2:

• Remove the JDK installation directory.

Uninstalling the Software from OS X

Each product in the bundle must be uninstalled separately.

To uninstall the IDE:

1. Shut down the software.
2. Drag the program folders or files to the Trash. Note that the default location for the IDE and application server is /Applications/NetBeans/ .

To uninstall the JDK and JavaFX 2.2:

• Remove the jdk1.7.0_80.jdk installation folder under /Library/Java/JavaVirtualMachines/ .

Finding Additional Documentation

NetBeans IDE is documented in the software’s help system, however, additional documentation about developing with NetBeans IDE is available at the NetBeans Documentation, Training & Support page.

For installation troubleshooting help please refer to the NetBeans IDE Installation FAQ.

See instructions for installing the JDK and JRE on Windows, Linux, and OS X at the Java SE Downloads page.

Providing Feedback

To report a bug or to request a feature for the JDK software, please refer to the following web site: http://bugreport.java.com/bugreport/index.jsp.

To submit your comments or suggestions about the JDK software, please send email to the OpenJDK Governance Board.

For NetBeans software development team contact information, or to learn more about NetBeans IDE and the NetBeans software community, visit the NetBeans Community Portal.

To submit feedback about this documentation, please send email to Documentation Feedback.

Источник