An Oracle blog about Java Technology

Java EE 8 Community Survey - Part 2!

David Delabassee
Software Evangelist

During the last 5 weeks, we have been positively surprised by the community responses on the first part of the survey. We have received a lot of valuable feedback! That means we have *a lot of data* to process, a really nice problem to face! Thanks to all who participated in Part 1! If you haven't, there still time to answer Part 1.

Part 2 of the survey is focusing on topics such as Cloud, Security, Logging, Deployment, Testability, etc. We are again soliciting your feedback on those different topics.

In a few weeks from now, once the results of the 2 parts have been distilled and summarized, we will share those results with the community. The next step would then be to ask you to help us prioritize those features.

Thanks in advance for helping us to set the initial directions of Java EE 8 by participating in Part 2 of the Community Survey.

Join the discussion

Comments ( 3 )
  • Claude Coulombe Wednesday, January 15, 2014

    1) Rich Internet App and Single Page Application in Java => controlling all the JavaScript on the client, in that sense, GWT (Google Web Toolkit) seems to be a good idea

    2) Cloud - Cloud - Cloud....

  • Todd Trimmer Wednesday, January 15, 2014

    Have a common interface, Attributable, for "contexts" such as ServletRequest, HttpSession, and ServletContext.

    interface Attributable {

    Object getAttribute(String)

    void setAttribute(String, Object)

    void removeAttribute(String)

    Enumeration<String> getAttributeNames()


    This will allow code that scans for an attribute in contexts, from finest to coarsest, not have to write so much boilerplate just to do the right downcasts.

  • guest Monday, February 17, 2014

    >GWT (Google Web Toolkit) seems to be a good idea

    Or maybe not, seeing that Google has just abandoned it?

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.