Over a million developers have joined DZone.

The Final Name for Java EE: A Vote

DZone's Guide to

The Final Name for Java EE: A Vote

Java EE will have to be renamed, and now it's up to the community to decide what it will be. Check out the two finalists and cast your vote!

· Java Zone ·
Free Resource

Build vs Buy a Data Quality Solution: Which is Best for You? Gain insights on a hybrid approach. Download white paper now!

As you're all likely aware, Java EE is migrating to the Eclipse Foundation. Formerly known as Java EE, the specification will no longer be governed by JCP. Instead, a truly open-source initiative named Eclipse Enterprise for Java was founded — abbreviated as EE4J. The EE4J project's aim is to drive standardization while being completely open for other competing vendors to add value to it.

The process of transitioning from Oracle and JCP to EE4J has been flawless so far, with one exception regarding naming issues. Oracle refused to let the community use the word "Java." There was an open letter by Java EE Guardians to Oracle, asking for permission not only to use "Java" in the new name for old Java EE, but to use it in package names as well. However, Oracle refused.

Well, the whole community kept suggesting new names for the modern successor of Java EE, and the list has been whittled to two names.

  • Enterprise Profile
  • Jakarta EE

Have your say and vote for the name of the next generation of Java EE.

Everyone from the community is welcome to vote. Voting closes on 23 February 2018.

Build vs Buy a Data Quality Solution: Which is Best for You? Maintaining high quality data is essential for operational efficiency, meaningful analytics and good long-term customer relationships. But, when dealing with multiple sources of data, data quality becomes complex, so you need to know when you should build a custom data quality tools effort over canned solutions. Download our whitepaper for more insights into a hybrid approach.

java ,oracle ,java ee ,ee4j ,enterprise profile ,jakarta ee

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}