I've been a zone leader with DZone since 2008, and I'm crazy about community. Every day I get to work with the best that JavaScript, HTML5, Android and iOS has to offer, creating apps that truly make at difference, as principal front-end architect at Avego. James is a DZone Zone Leader and has posted 639 posts at DZone. You can read more from them at their website. View Full User Profile

Have You Adopted Java 7 Yet?


Java 7 has been available for a while now, and according statistics that Jelastic ran, it's market share is growing, albeit slowly. The article states that Java 7 accounts for 17% of the market while Java 6 still holds 83%.  With Java still holding it's own on the latest TIOBE index, there's no doubt that it's not losing it's appeal to developers and corporations. But have you, or your company, moved to Java 7? I'd like to run a poll here on JavaLobby to see where the community is on Java 7 adoption.

It would also be interesting to hear why you did (or didn't) move to Java 7?

We have adopted Java 7
16% (293 votes)
We're still on Java 6, with no plans to change
49% (888 votes)
We'll move to Java 7 later this year
25% (455 votes)
We haven't even moved to Java 6!
9% (170 votes)
Total votes: 1806


Greg Hall replied on Thu, 2012/02/09 - 8:41am

We will move to Java 7 once it's available on OSX.

Jonathan Fisher replied on Thu, 2012/02/09 - 8:20pm

Most will wait for better vendor support needed for Java7. For those who need invokedynamic, the time to move is now, unless you're on OSX.


Good god this rich text editor is horrid. 

James Sugrue replied on Fri, 2012/02/10 - 6:46am

Interesting - we're one day into the poll and it seems that over half of the people who responded are happy with Java 6. Surely there are more people out there who are using Java 7? Like Lukas mentioned, Java 6 v30 is very stable: unless you're desperate for the features added in 7, maybe Java 8 is what everyone is waiting for? James

Charles (Ted) Wise replied on Fri, 2012/02/10 - 8:45am

It's not GA on OS/X yet, so there won't be any movement for us. In addition, there appear to be display issues with Java 7 that manifest in IntelliJ. Honestly there just isn't anything earth shattering in Java 7 that we're missing. We'll move once it's on OS/X and has had a few more points releases to stay current with updates, security fixes and invokedynamic (though invokedynamic won't help us until Groovy 2.0).

Matthew Adams replied on Fri, 2012/02/10 - 10:33am

JDK 7 is a pain because of the JDBC DataSource interface change (addition of method getParentLogger()) breaks everything. Poo. :(

Andy Gibson replied on Sat, 2012/02/11 - 12:19am

Its a PITA to install on Ubuntu and there really isn't that much new stuff to get all excited about.



Jim Lombardo replied on Mon, 2012/02/13 - 12:32pm

We'll move once it's available on OSX

Mason Mann replied on Wed, 2012/02/22 - 8:58am in response to: Matthew Adams

Yeah, there's NO FUCKING excuse for breaking a public interface.

Kai Wähner replied on Thu, 2012/02/23 - 8:02am in response to: James Sugrue

@James: I think you interpret it wrongly: "Interesting - we're one day into the poll and it seems that over half of the people who responded are happy with Java 6."

You cannot deduce this from the question. The answers do not say if someone is happy or why someone did (not) change yet. Therefore, you should either change the question or the answers :-)

Many people would like to migrate to Java 7 probably to use its advantages. But it is not allowed / reasonable in several projects...

Thomas Nagel replied on Mon, 2012/03/12 - 3:52am

We have more trouble with JBoss'es waving and unclear change agenda.

The thing about the JCP that we worry about are the malfuctions of EJB3. Has any of those Java-Guru-Gods ever written a real application with EJB3 or tried migrating an EJB 2 app with 250+ tables to EJB3 ? I doubt very much. In my eyes, EJB3 is only fit to work with mysql, a mere table management and no transactions or referential integrity included. In short: we hate to give up working code only because the big majority has changed its mind and the builders of the frameworks will stop supporting what we use.

What we need from a real next-step Java version is (1) having an advanced swing-descendant for GUI with components matching JSF-libs and including a graphic designer and (2) working out-of-the-box with modern servers over secure connections and (3)  from app servers support for SQL and NOSQL in an understandable way with a clear API supporting internationalization.


greetings from germany,


Eric Rich replied on Tue, 2012/03/13 - 10:29am

Anyone else notice incredibly slow XML parsing with Java 7? We tried to support Java 7 but found XML parsing to be quite a bit slower than in Java 6. We'll support Java 7 once we figure out the XML performance problem later this year.

Reputation Advo... replied on Thu, 2012/06/14 - 2:42am

Haven't adopted Java 7 yet. This is the first time that I heard about it. I will definitely try this one out. ReputationAdvocate.com

Kookee Gacho replied on Mon, 2012/06/18 - 5:32am

A major update to Java that was launched on July 7, 2011and was made available for developers on July 28, 2011. The development period was organized into thirteen milestones; on February 18, 2011, milestone 13 (the last milestone) was reached.-Dr. Marla Ahlgrimm

Ayurveda Yatan replied on Sat, 2013/12/07 - 10:50am

 However, menopause throughout females can't satisfactorily always be explained basically because long term "stopping of the regular periods", because in fact what on earth is going on on the uterus is quite secondary on the method; it is what on earth is going on on the ovaries be the important component.

Perimenopause Symptoms

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.