Java EE Is Moving To the Eclipse Foundation (adtmag.com)

Oracle has chosen the Eclipse Foundation to be the new home of the Java Platform Enterprise Edition (Java EE), the company announced this week. Oracle made the decision in collaboration with IBM and Red Hat, the two other largest contributors to the platform. From a report: "The Eclipse Foundation has strong experience and involvement with Java EE and related technologies," wrote Oracle software evangelist David Delabassee in a blog post. This will help us transition Java EE rapidly, create community-friendly processes for evolving the platform, and leverage complementary projects such as MicroProfile. We look forward to this collaboration." Mike Milinkovich, executive director of the Eclipse Foundation, is optimistic about this move, which he said is exactly what the enterprise Java needs and what the community has been hoping for.

Comments

Re:Why does a language need an "Enterprise Edition

[bws111]

Java is not just a language, it is also a platform (JVM, APIs, etc). The different editions are for the plaform not the language. So there is a platform for 'normal' usage (SE), a platform for long-running, network intensive applications (EE), and a platform for lightweight use (ME).

Re:Why does a language need an "Enterprise Edition

[angel'o'sphere]

Java is not a compiler.

It is a huge set of specifications, a huge set of standard libraries, and a mountain of open source frameworks and platforms. And VMs ...

SE: standard edition, mainly for desktop apps, but the line to EE is blurry
EE: enter prise edition, defines standards for accessing DBs, do OR mapping (via annotations (*)), have annotation(*) based REST/SOAP services and build in tools to support development or out of the box deployment

In other words, if you want to run a C++ web service, you first need a web server (extra download and install) where you can deploy your *.so/*.dll to, then you configure something that the web server knows what requests to route to your plug in.

In Java EE, there is a build in web server, and you simply deploy the *.dll analogon (a *.war) and the server configures everything automatically, based on annotations (*)

(*) an annotation can be considered as a smart comment. The compiler puts it into the object code and the deployment environment interprets it (with framework support) and weaves the necessary missing code around it or uses reflection to orchestrate what ever the annotations are supposed to do.