Updates From Java World
If you are interested in reading the latest draft, it is available for download on the EJB spec java.net project page: http://java.net/projects/ejb-spec. On this page you can also subscribe to the users mailing list to read the ongoing discussions and provide your input.
The much awaited Project Jigsaw whose aim is to design and implement a standard module system for the Java SE Platform, and to apply that system to the Platform itself and to the JDK seems to be getting deferred to Java 9 which is expected to available by 2015.
In announcing the deferment, Mark Reinhold, chief architect of the Java platform group at Oracle, cited insufficient time and technical issues. "The proposed development schedule for Java 8 expects work on major features to be finished by May 2013 in preparation for a final release around September," Reinhold said in a blog post.
Oracle has posted in the jdk8-dev mailing list the JDK 8 milestone and release dates for review and feedback. Following dates for the JDK 8 development milestones have been proposed.
Details for each milestone has not been specified, but will be posted as soon as it is available to help the early testing process. M6 is expected to be feature complete (FC). This is when all features and new test development would be completed. JDK 8 is targeted to be released by September 2013. This is to give at least as much time to stabilize JDK 8 as was needed in JDK 7.
Between M6 and GA, the tolerance for changes will decrease in steps. General bug fixing is allowed from early February till early April 2013. By early April 2013, only P1-P3 bugs will be fixed. By mid-June 2013, only showstoppers will be considered.
Component JSRs will not need to follow the proposed dates until early May 2013. There is also a discussion about adding M7, a Developer Preview milestone to the JDK 8 schedule. This will be the best time to encourage individual developers, open source projects, and JUGS to help test the JDK. This should help identify, prioritize and fix issues faster, and hopefully prevent a repeat of the Lucene issue, where a loop optimization bug was discovered by the Apache Lucene developers a few days before the Java 7 release.
Here is the download link for the same http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html
Oracle has published the first release candidate for JDK 7, the long-awaited next version of Java set to officially debut on July 28.
On Thursday, during a webcast from the Oracle bunker in Redwood City, California, Java chief architect Mark Reinhold said that the most significant thing about the new release is that "we're finally shipping it". Though it has been nearly five years since the release of Java 6, the new version isn't exactly a huge leap forward.
Finally JRockit is no longer tied to Oracle products: you can download it for what look like the same terms as the old Sun JDK. JRockit is way faster then HotSpot after a suitable warmup period.
JRockit is known to be more efficient and super fast as compared to Sun JDK in production environments. JRockit's garbage collector is really nice, too; it can be made predictable, which is something that's bugged the Sun JVM users for years.
Mission Control and Real time still are commercial offerings. Well worth it, though, and I'm really happy to see JRockit free. Looks like you need an Oracle Network login to get it, still, though.
Apache Software Foundation (ASF) has added Java Enterprise Edition 6 web applications support to Tomcat 7.0.6. Apache Tomcat's open source implementation of Java Servlet and Javaserver Pages technologies has added the support in the latest release.
"This is the first stable release of the Tomcat 7 branch", blogged Apache developer Mark Thomas. "This release contains a number of bug fixes, further performance improvements in session management and several enhancements to the memory leak detection and prevention features," he added.
The Tomcat 7.0.6 updates are catalogued on the Apache changelog, which is chock full of contributions from the volunteer team that added the 7.0.6 feature set. The biggest distinction for Tomcat 7.0.6 is that it has been upgraded to version 3.0 of the Servlet API. It has also been updated to include version 2.2 of Javaserver Pages. The updated versions of the Servlet API and Javaserver Pages have only recently been signed off as part of the Java Enterprise Edition 6 ratification.
Read more: http://www.theinquirer.net/inquirer/news/1937528/apache-announces-tomcat-706#ixzz1BVaH4HPN
The 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.
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.
Last month Oracle renominated Apache to the Java Executive Committee because we valued their active participation and perspective on Java. Earlier this week, by an overwhelming majority, the Java Executive Committee voted to move Java forward by formally initiating work on both Java SE 7 and SE 8 based on their technical merits. Apache voted against initiating technical committee work on both SE 7 and SE 8, effectively voting against moving Java forward. Now, despite supporting the technical direction, Apache have announced that they are quitting the Executive Committee. Oracle has a responsibility to move Java forward and to maintain the uniformity of the Java standard for the millions of Java developers and the majority of Executive Committee members agree. We encourage Apache to reconsider its position and remain a part of the process to move Java forward. ASF and many open source projects within it are an important part of the overall Java ecosystem.