Java EE devotees plot to seize control from Oracle

Paul Krill |
July 5, 2016

Tired of Java EE's languishing, two groups may develop their own parts of Java -- but don't call it a 'fork'

Features under consideration cover security, Java Message Service, and Jax-RS. HTTP 2 also could be developed, but this capability would be hard to implement separate from the JCP, since it is directly dependent on Java servlet API, Rahman said. Java EE Guardians would like to avoid moving ahead outside the JCP, so it'll wait about a month before deciding whether to proceed on its own, he added.

"There's a feeling of a lack of leadership," said MicroProfile participant Sharples. Oracle's involvement, he said, has tailed off. "We've seen very little detail about what Java EE 8would look like." Oracle is in charge of many of the Java specifications, Sharples noted, so Java EE "really can't move forward without Oracle's investment."

Even a member of the JCP Executive Committee, which oversees revisions to the platform, vouches for Oracle's neglect. "Judging simply by the facts, that out of 12 Java EE 8 JSRs (Java Specification Requests) -- including JCache, which is a roll-over from EE 7 if included -- only one new JSR has recently filed [for] public review," said Werner Keil.