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.
The rising concerns over Oracle's very slow Java pace
A few years ago, Oracle had jumpstarted Java's development and improved its security after it took over from Sun. But all that momentum -- and the goodwill that came with it -- seems to be going by the wayside as Java EE has languished.
"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.
At Java EE Guardians, Rahman, said the group has collected nearly 2,000 signatures to its petition urging Oracle to move Java EE forward.
Oracle, which became the de facto steward of the Java platform when it acquired Java founder Sun Microsystems in early 2010, declined to discuss the issues around Java EE.
Sign up for CIO Asia eNewsletters.