Mike Milinkovich, executive director of the Eclipse Foundation, says the move is all about breathing new life into the Java Enterprise Edition platform. In the fall of 2017, Oracle decided that it had had enough and, at the urging of a group of vendors that included IBM, Red Hat, and others, it agreed to relinquish control of Java EE to the Eclipse Foundation, which is the driving force behind the Java-based integrated development environment (IDE) of the same name. However, over the past few years, the excitement over JEE has waned and the pace of change has slowed considerably.

That included JSRs like Java servlets, Java ServerPages (JSP), Enterprise JavaBeans (EJBs), Java ServerFaces (JSF) J2EE Connector Architecture (JCA), the Java Persistence API (JPA) and the Java Message Service (JMS), among others. Under the J2EE moniker, companies readily adopted a variety of Java Service Requests (JSRs), or JEE specifications, delivered under the Enterprise Edition umbrella. In the early 2000s, prior to the Sun acquisition, the pace of innovation was heavy, as Java and JEE spread throughout corporate America and the entire world. That includes defining not just the core Java language, but having a big hand in everything else governed through the Java Community Process (JCP), including the Java Virtual Machine (JVM), the Standard Edition (JSE) runtime, and the Java Enterprise Edition (JEE) platform, which provided enterprise-level capabilities for running Java applications at scale, including use of web services and distributed execution of code.

Since it bought Sun Microsystems back in 2010, Oracle has been fully in charge of Java.

As part of an agreement with Oracle, the tech giant will give up control over the platform to Eclipse Foundation, which has big plans to remake enterprise Java for the emerging cloud world. Hello, Jakarta EEĭevelopers who use Java Enterprise Edition will be happy to know that the development and runtime platform is gaining new life as Jakarta EE.

Java ee developers