Skip to main content

InfoQ: JDK 7 is Feature Complete

InfoQ: JDK 7 is Feature Completehe JDK 7 project says it has hit a major milestone, with the first feature complete build shipping in build 123. Henrik StÃ¥hl, who is responsible for product strategy in the Java Platform Group and is an official spokesperson for Oracle on Java SE, blogged
This means that development and QA have finished all planned feature and test development work in the release and are moving the focus to testing and bug fixing on all supported JDK 7 platforms. This is a major step towards JDK 7 General Availability (GA) and implies that we are tracking close to the plan published on
The OpenJDK website includes a complete list of features, and shows those which have been deferred over to JDK 8 or later. Mark Reinhold’s blog lists a couple of features which are outstanding, which will be integrated post the Feature Complete release. These are the updated XML Stack and the Enhanced JMX Agent and MBeans. The late integration of these features is not expected to affect the overall schedule.
"Enhanced JMX Agent and MBeans" is a recent addition to the schedule. Ported from JRockit, it is an implementation-specific enhanced JMX management agent which is intended to make it easier to connect to the platform MBean server through firewalls, together with a richer set of MBeans which expose additional information about the internal operation of the VM. This represents the first public steps in a major project to integrate features from JRockit into Hotspot, which Reinhold talked about last year.
The first important date for people wanting to get involved in testing the releases is February 17th, when the Developer Preview release, effectively a beta, is expected to be available. Beyond that Java 7 should hit general availability on the 28th July, according to the schedule, though the release could still be delayed if the Expert Groups for the JSRs included in Java SE 7 (203292334336) decide to introduce changes which cannot be accommodated within the existing schedule.
Support for Lambda expressions, Modularity (project Jigsaw), the Swing Application framework (JSR 296), and some smaller language enhancements from project Coin were dropped from Java 7. It is expected that some of these features will be included in Java 8, expected in late 2012.


Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Spring - Operations with jdbcTemplate

This class manages all the database communication and exception handling using a java.sql.Connection that is obtained from the provided DataSource. JdbcTemplate is a stateless and threadsafe class and you can safely instantiate a single instance to be used for each DAO.

Use of Callback Methods
JdbcTemplate is based on a template style of programming common to many other parts of Spring. Some method calls are handled entirely by the JdbcTemplate, while others require the calling class to provide callback methods that contain the implementation for parts of the JDBC workflow. This is another form of Inversion of Control. Your application code hands over the responsibility of managing the database access to the template class. The template class in turn calls back to your application code when it needs some detail processing filled in. These callback methods are allowed to throw a java.sql.SQLException, since the framework will be able to catch this exception and use its built-in excepti…