Log Message:
Update to 1.7.65 (7u65)

* Use openjdk7-1.7.60 based bootstrap kits to avoid headlessawt related errors.
  Confirmed under NetBSD/{amd64,i386} 5.2.2, NetBSD/{amd64,i386} 6.1.1,
  NetBSD/{amd64,i386} 6.99.47, and DragonFly/amd64 {3.6.1,3.8.1}.
* Drop pre-3.6 DragonFly support.
* Drop unused distfiles from icedtea-extra.mk.

Changelog: for Oracle Java 7u65
From: http://www.oracle.com/technetwork/java/javase/7u65-relnotes-2229169.html

Java™ SE Development Kit 7, Update 65 (JDK 7u65)

The full version string for this update release is 1.7.0_65-b17 (where \ 
"b" means "build"), except for Windows, where the version \ 
string is 1.7.0_65-b20. The version number is 7u65.
Highlights

This update release contains the following enhancements and changes:

    New Features and Changes

IANA Data 2014c

JDK 7u65 contains IANA time zone data version 2014c. 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 7u65 are specified in the following table:
JRE Family Version 	JRE Security Baseline
(Full Version String)
7 	1.7.0_65
6 	1.6.0_81
5.0 	1.5.0_71

For more information about security baselines, see Deploying Java Applets With \ 
Family JRE Versions in Java Plug-in for Internet Explorer.
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 7u65) will expire with the release of \ 
the next critical patch update scheduled for October 14, 2014.

For systems unable to reach the Oracle Servers, a secondary mechanism expires \ 
this JRE (version 7u65) on November 15, 2014. After either condition is met (new \ 
release becoming available or expiration date reached), the JRE will provide \ 
additional warnings and reminders to users to update to the newer version. For \ 
more information, see JRE Expiration Date.
JavaFX Release Notes

This JDK release includes JavaFX version 2.2.65.
New Features and Changes

New Java Control Panel option to disable sponsors

Currently, to disable sponsor offers at the time of installation, the user can \ 
de-select the option during installation or can pass SPONSORS=0 as a commandline \ 
option.

In this release, a new Java Control Panel(JCP) option to disable sponsors is \ 
available. To use this option, go to JCP's "Advanced" tab, and check \ 
or uncheck "Suppress sponsor offers when updating Java".

This option is applicable to 32 and 64 bit Windows operating systems.
New JAXP processing limit property - maxElementDepth

A new property, maxElementDepth, is added to provide applications the ability to \ 
set limit on maximum element depth in an xml file that they parse. This may be \ 
helpful for applications that may use too much resources when processing an xml \ 
file with excessive element depth.

    Name: http://java.sun.com/xml/jaxp/properties/maxElementDepth
    Definition: Limit the maximum element depth
    Value: A positive integer. 0 is treated as no limit. Negative numbers are \ 
treated as 0.
    Defaule value: 0
    System property: jdk.xml.maxElementDepth

For more details, see Processing Limits from JAXP tutorial trail.

See 8031541 (not public).
Bug Fixes

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

For a list of bug fixes included in this release, see JDK 7u65 Bug Fixes page.

The following are some of the notable bug fixes in this release:

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.

See 8019274.

Area: other-libs/corba
Synopsis: org.omg.CORBA.ORBSingletonClass loading no longer uses context class loader

The system property org.omg.CORBA.ORBSingletonClass is used to configure the \ 
system-wide/singleton ORB. The handling of this system property was changed in \ 
the 7u55 release to require that the system wide/singleton ORB be visible to the \ 
system class loader.

In this release, the handling of this system property has been reverted to match \ 
the behavior found in JDK versions prior to 7u55 release, i.e. the singleton ORB \ 
is once again located using the thread context class loader of the first thread, \ 
to call the no-argument ORB.init method. The change is made to support \ 
applications which depend on this behavior.

Note that this change is applicable to 8u20, 7u65, 6u85 and 5.0u75 releases. For \ 
JDK 9, the new behavior, where the system wide/singleton ORB needs to be visible \ 
to the system class loader, will continue.

See 8046603.
Known Issues

Area: xml/jax-ws
Synopsis: JAF initialization in SAAJ clashing with the one in javax.mail

After initialization of SAAJ components, the javax.mail library may fail to work \ 
under certain circumstances, which in turn could break the javax.mail's JAF \ 
setup.

A possible workaround is to re-add the javax.mail handler before using \ 
javax.mail API:
MailcapCommandMap mailMap = (MailcapCommandMap) CommandMap.getDefaultCommandMap();
mailMap.addMailcap("multipart/mixed;;x-java-content-handler=com.sun.mail.ha \ 
ndlers.multipart_mixed");

See 8043129.