By Madison Moore
Translation 丨 lloog
Oracle plans to promote Java EE in a more open and collaborative community in order to make Java EE more agile and flexible.
Oracle announced on its blog that following the promising progress of Java EE 8, Oracle is now considering ways to make Java EE more open and accessible to the open source community. In other words, Oracle wants to give up the lead in Java EE, hoping that the open source community will have more power to promote Java EE.
“Java EE is highly successful, with a competitive market, compliant implementations, widespread adoption of personal technologies, a vast ecosystem of frameworks and tools, and countless applications that bring value to enterprises and end users,” Oracle said in a blog post. But while Java EE is open source with community participation, the process is generally not considered agile, flexible, or open, especially when compared to other open source communities. But we want to do better. “
According to Oracle, in order to “adopt more agile processes, enable more flexible licensing, and change governance processes.” Moving Java EE technology to an open source basis may be the right next step, and Oracle also plans to explore this possibility with the developer community, its licensees, and some candidate foundations to see if they can move Java EE in this direction.
“We believe a more open process that does not rely on a single vendor as a platform leader will encourage greater participation and innovation and will be in the best interest of the community,” the blog reads.
While there are many details to be fleshed out, Red Hat is optimistic about Oracle’s decision to move forward with Java EE on an open source basis, said John Clingan, Senior principal product manager at Red Hat. Open source software company Red Hat is built on open source principles.
“We think that bringing Java EE under the umbrella of the open source community is a very positive move that will benefit the entire enterprise Java community,” Clingan said.
Since Java EE has been in development for nearly two decades, to meet market demand, Clingan said red Hat felt it needed a two-tier approach to grow Java EE faster.
“This includes Java EE as a standard that should move at a measured pace, and Eclipse MicroProfile as an open source project as an innovation engine that can bring new functionality to Java EE developers more quickly,” Clingan said. He adds that configuring JSR commit is one example.
As a member of the Eclipse MicroProfile community, Red Hat plans to continue advancing and delivering functional specifications within the Eclipse MicroProfile community as an effort to move Java EE onto the ground. As a licensee, Red Hat(along with JBoss prior to the acquisition) pioneered the idea of an open standard enterprise application platform and open source collaboration that, according to Clingan, really drove the adoption of open source as “the heart of the enterprise.”
Clingan said Red Hat is leading CDI and Bean validation of Java EE-related JSRs, participating in multiple additional Java Ee-related JSRs, and targeting the JBoss Enterprise Application platform as a fully Java EE-compliant platform.
As Java EE evolves, Oracle wrote, it intends to meet the needs of its developers, end users, customers, technology consumers, partners and licensors. Clingan said Java EE has the opportunity to grow more and have a more permissive license that will encourage new contributions, new implementations and distributions. Moreover, end-user developers should be able to use Java EE-related technologies more quickly.
In addition, Oracle will support existing Java EE implementations and future Java EE implementations.
