Skip to main content

The Sharpest Lives

Posted by editor on March 26, 2009 at 8:51 AM PDT

How the OpenJDK team plans to get to JDK 7

OK, here we go. Here's the roadmap that gets us to JDK 7, and what we'll pick up along the way. Mark Reinhold's latest post, unassumingly titled JDK 7, lays out the path that OpenJDK will take over the next few months to get to a JDK 7 release in early 2010.

At Devoxx back in December I presented a list of candidate features for JDK 7 (video, interview); more recently, at FOSDEM, I discussed that list as well as the high-level schedule and the means by which we plan to deliver the release (slides, audio/video).

The high-level schedule is now available on the JDK 7 Project page in the OpenJDK Community along with a detailed feature list, the near-term build and integration schedule, and the long-term, build-by-build calendar.

The JDK 7 feature list, like that of any large software project, is provisional and subject to change based upon new information and new proposals.

So what can we make of the features? JSR 296, the Swing Application Framework that some had feared for the well-being of, is still part of JDK, with the high-level integration schedule suggesting we'll see it in or around July, in the Milestone 5 timeframe. On the other hand, the Joda Time-inspired JSR 310 Date and Time API is living up to its "marked as inactive" status and has apparently fallen off the JDK 7 radar.

Still, a lot of the other interesting items mentioned by Mark as JDK 7 candidates are in the feature list, including less talked-about features like concurrency and collections updates (Fork/Join, Phasers, Fences, etc.) and Swing Updates including JXLayer and JXDatePicker, which would apparently be the first SwingX components integrated into core Java.

So, take a look at the list and the schedule, and let us know what you think.

In Java Today, The H went to Qcon and sat down with Patrick Curran, chair of the Java Community Process for a chat about how the JCP is changing and looking for more transparency in all aspects of its work. In Interview: Patrick Curran, chair of the JCP, they discuss the status of JSR 310 (the Joda Time-inspired date and time API for Java 7), Apache's ongoing TCK licensing dispute, the openness of the JSR process, iterative spec development ideas, and more.

Following an indecisive earlier poll about Swing look-and-feels, Jasper Potts has revised his questions and reposted them as Breakdown of what should be default LAF for Java 7. "After watching the voting and reading the comments I have noticed two things: First is from 30 votes to 800 votes the percentages have hardly changed which means we seem to be falling on a conclusion. Native LAF has varied from 59% to 63% so nothing major and is a clear winner. The second point is there seems to be different answers for Windows and Unix and good arguments that maybe they should not be the same so let me start a new poll with them split and see if I am right. I will split the poll into 3 categories Windows, Unix GTK and Unix KDE."

Today's Weblogs finds James Gosling
Wandering the UK and talking with developers there about Java. "One thing I kept getting asked about was using real-time for transaction servers. The reason they're all interested is because the real-time VM has a garbage collector that has guaranteed maximum pause times. While this does work very well, it is often overkill."

Fabrizio Giudici says Let's fork BeansBinding. "I hope/presume that there is some other guy willing to do that, so it will be a genuine community effort. It doesn't seem a hard task, since the code looks clean (more info after I run FindBugs on it), there are 126 classes in total, of which only 43 are new, the others a forked, patched implementation of the EL language."

Next, in Footprint Project adopts Maven 2, Felipe Gaucho announces that the "Footprint project was updated to Maven 2.0 and published in the Maven 2 repository."

In today's Forums, gjparson is trying to get network code working on actual Blu-Ray devices, in
Re: [BD-J-DEV] Network connection issues - again. "My BD-Live app runs fine on my pc running TMT, but throws a socket permission exception on my Samsung BD-P1500 player that's cable connected to the Internet and to a Samsung HDTV. I have run player updates via the Internet with this hardware configuration, and the player itself is set to "Allow All" BD-Live content. So there doesn't appear to be any problem with the hardware setup. I have researched this issue in your book and in various project, conference and online documents and even source code files. I have created a grantor keystore and used the BDCredentialSigner tool to sign the PRF, but so far nothing has worked. Accessing publicly available Web documents would seem to be a trivial task, but with the many BD-J security restrictions it has been a showstopper for me, and perhaps for a few others out there."

Scott Oaks points out a possible bottleneck in
Re: Debugging Glassfish CPU usage. "The most likely culprit seems to me to be the network -- I did notice in some of the stack dumps that a few glassfish threads were blocking writing data back to the clients, which would normally only happen if there is a network issue. I wonder if running tcpdump/snoop on both the client and server machines would show any delays. Or seeing how much ftp thoughput you get during those 30-second intervals. Or even simple ping tests (or traceroutes) could show a long time delay."

Finally, writtmeyer talks about how to use Java Messaging Service in GlassFish in the reply Re: newbie question. "Yes. The OpenMQ JMS implementation is part of GlassFish. GlassFish also supports Message Driven Beans. See here for how to configure it: This excellent article might also be of interest to you: I am not sure if everything is available in the current v3 builds. But all v2 builds have a JMS implementation included - and the final release of v3 will have one as well."

Current and upcoming Java

Registered users can submit event listings for the href=""> Events Page using our href="">events submission form.
All submissions go through an editorial review before being posted to the

Archives and Subscriptions: This blog is delivered weekdays as
the Java
Today RSS feed
. Also, once this page is no longer featured as the
front page of it will be
archived along with other past issues in the href=""> Archive.

How the OpenJDK team plans to get to JDK 7


I hear a lot of things about JDK 7, but none about Java SE 7. Is Stephen Colebourne right about Sun's (questionable) tactics on the future of Java?