Red Hat lays out plans for Java EE 7

By Alex Handy

April 19, 2011 — (Page 1 of 2)
Java EE hasn't been receiving the same amount of attention its open-source brethren have over the past year. While the JCP and the OpenJDK focused heavily on nailing down the plans for Java SE 7 and 8, as well as plans for the OpenJDK itself, Java EE 6 has quietly been moving toward implementation within IBM and Oracle.

And while Java EE 6 brought initial modularity changes along with the addition of REST support, Java EE 7, which began life as JCP standards proposals in April, looks to repair many of the historic problems with the platform.

Rich Sharples, director of product management at Red Hat, said that the Java EE 7 proposals created by his company are initial ideas for the future of the platform. The work ahead will first involve forming expert committees around these new ideas, then formulating and formalizing specifications for the future of Java.

Sharples said the vision for Java EE 7 includes four main goals: ease of deployment, support for HTML5, support for the cloud, and the deprecation of unused portions of the framework. The first and last of these goals were also pursued, to a small degree, with Java EE 6. In EE 7, he, they should receive a lot more attention.

“Because of Java EE's focus on compatibility, there is a feeling it's grown rather large," said Sharples. "We've added a lot to the Java EE platform. With Java EE 6, a number of APIs were announced to be pruned or deprecated, and they will be pruned in Java EE 7."

Among all of those proposed areas of improvement is one major proposal that caught the eye of John Rymer, a Forrester vice president and primary analyst. That improvement is a standardized cache API for Java EE.

“They're proposing to standardize the elastic caching APIs," he said. "Oracle has Coherence, which has a lot of usage, and it has an API. This is an important capability for scaling Web applications, not only in Java, but in .NET as well. There's no standard API.

Related Search Term(s): Java, Red Hat, OpenJDK

Pages 1 2

Share this link: http://sdt.bz/35458

Technorati

Digg

Slashdot

Facebook

Friendfeed

Twitter

del.icio.us

Java 8 won't be modular OpenJDK 8 ditches Project Jigsaw in order to meet end-of-summer release date

Red Hat unveils Enterprise Application Platform 5.0 The new platform will start out in Amazon's Elastic Compute Cloud and includes a set of Java tools

Red Hat prepares complex events processing for SOA Updates to JBoss Enterprise SOA Platform and JBoss Operations Network lay the groundwork for enhanced CEP and rules management. Beyond that, new security features have been implemented in Enterprise SOA Platform.

Comments

04/19/2011 04:44:31 PM EST

I think the people complaining about complexity haven't looked at J2EE5 or 6. I agreed with them on earlier version. The improvements have been huge, and it now takes very little framework related effort to put together an application. Much of the credit goes to the introduction of annotations along with bypassing a lot of infrastructure no one used in the first place. The JAX-RS (REST) and JSF 2 support in 6 have been particularly useful for my new development. It gives me a headache to have to go back and modify the older applications now.

United StatesJOTN

04/21/2011 11:08:44 PM EST

Spring isn't exactly the alternative to JavaEE as it builds primarily on Java and unlike JavaEE it is backed mainly by one vendor (vmware) but there is an alternative movement around OSGi which Spring also bets on quite heavily.

United KingdomWerner Keil