At last year's JavaOne Anil Gaur, vice president of Oracle's Cloud Application Foundation group, announced a survey to help determine priorities for the revised road map for Java EE. The survey results are now available, together with the revised Java EE 8 proposals.

Nearly 1,700 Java users worldwide took part in the Java EE Survey conducted in September and October 2016. Respondents were asked to rank the importance of 21 component technologies in the company's revised Java EE Roadmap on a scale of 1 to 5, with 1 equaling "not important," and 5 equaling "very important."

This chart summarizes the results:

Although there was some variation between inexperienced users of Java EE (n=287) and those with  more than 2 years experience (n=1406) all groups ranked REST services and HTTP/2 as most important while Management, JMS and MVC were ranked low by all respondents.

This table summarizes Oracle's original and revised Java EE 8 proposals, focusing on areas of new API development:

The Oracle blog post outlines these conclusions about the revised Java EE 8 road map:

• REST (JAX-RS 2.1) and HTTP/2 (Servlet 4.0) have been voted as the two most important technologies surveyed, and together with JSON-B represent three of the top six technologies. Much of the new API work in these technologies for Java EE 8 is already complete.  There is significant value in delivering Java EE 8 with these technologies, and the related JSON-P updates, as soon as possible. 
  
  
• CDI 2.0, Bean Validation 2.0 and JSF 2.3 were not directly surveyed, but significant progress has been made on these technologies and they will be included in Java EE 8.
  
  
• We considered accelerating Java EE standards for OAuth and OpenID Connect based on survey feedback.  This could not be accomplished in the Java EE 8 timeframe, but we’ll continue to pursue Security 1.0 for Java EE 8.
  
  
• At JavaOne, we had proposed to add Configuration and Health Checking to Java EE 8, and these technologies rank reasonably high in survey results.   However, after additional review we believe the scope of this work would delay overall Java EE 8 delivery.  We have concluded it is best to defer inclusion of these technologies in Java EE in order to complete Java EE 8 as soon as possible.
  
  
• Management, JMS, and MVC ranked low in survey results, and this ranking supports our proposal to withdraw new APIs in these areas from Java EE 8. We have withdrawn the JSRs for Management 2.0 (JSR 373), and JMS 2.1 (JSR 368), and are investigating a possible transfer of MVC to another community member or organization in order to complete JSR 371 as a stand-alone component.

More Information

Java EE Survey Results and Java EE 8 (pdf)

Java EE 8 - Community Survey Results and Next Steps

Related Articles

Java Guardians To The Rescue Of Java EE

Opinions Sought On Java EE 7

To be informed about new articles on I Programmer, sign up for our weekly newsletter, subscribe to the RSS feed and follow us on Twitter, Facebook or Linkedin.

Comments

Make a Comment or View Existing Comments Using Disqus

or email your comment to: comments@i-programmer.info