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 openjdk.java.net.
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 (203, 292, 334, 336) 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.

Comments

Post a Comment

Popular posts from this blog

Quicksort implementation by using Java

 source: http://www.algolist.net/Algorithms/Sorting/Quicksort. The divide-and-conquer strategy is used in quicksort. Below the recursion step is described: 1st: Choose a pivot value. We take the value of the middle element as pivot value, but it can be any value(e.g. some people would like to pick the first element and do the exchange in the end) 2nd: Partition. Rearrange elements in such a way, that all elements which are lesser than the pivot go to the left part of the array and all elements greater than the pivot, go to the right part of the array. Values equal to the pivot can stay in any part of the array. Apply quicksort algorithm recursively to the left and the right parts - the previous pivot element excluded! Partition algorithm in detail: There are two indices i and j and at the very beginning of the partition algorithm i points to the first element in the array and j points to the last one. Then algorithm moves i forward, until an element with value greater or equal
Post a Comment
Read more

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know. Symptom: 1.        The JVM became Out of memory when creating big consumption report 2.        Those JRTemplateElement-instances is still there occupied even if I logged out the system Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.     The clearobjects() method in ReportThread class has not been triggered when logging out Action I tried:      About the Virtualizer: 1.     Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.     Not use any FileVirtualizer for cache the report in the hard disk Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory        About the work around below,      I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object        
1 comment
Read more

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"/>
4 comments
Read more