We are an independent grassroots group of people committed to moving the Java EE platform forward and evangelizing it. We believe that standardizing the core technologies used to build enterprise applications is better than competing proprietary solutions. Closed ecosystems stymie innovation, cripple careers, and harm end-users.
Java EE has been the most successful set of open standards for developing enterprise applications ever. It has been the linchpin of the Java platform’s domination and there isn’t a Java application that doesn’t depend upon at least one Java EE technology. It is the only enterprise technology with a rich ecosystem of vendors who not only compete but cooperate to define a solid set of core technologies.
The health of the Java ecosystem is dependent upon Java EE. Java EE development is one of the largest drivers of Java usage. The evidence that Java EE is important to the overall adoption of the Java platform is impossible to ignore:
- Hundreds of thousands of applications worldwide are written in Java EE, many of those applications are regularly being brought to light. Even applications and frameworks that claim they do not use Java EE are in fact heavily dependent on many Java EE APIs today and going forward, regardless of trends like cloud or microservices. Just some of these APIs include Servlet, JAX-RS, WebSocket, JMS, JPA, JSF and so much more.
- There were no less than 4,500 input points to the groundbreaking survey to determine Java EE 8 features.
- In major survey after survey developers continue to show their strong support for Java EE and its APIs.
- Java EE vendors and products are highly profitable and the backbone of commerce.
- Few multi-vendor open standards are as widely implemented, supported, depended upon or as widely participated in as Java EE.
- There is an extremely passionate, responsible community behind Java EE – most technologies would be hard pressed to find anything like the Java EE community.
The Java EE Guardians was formed in 2016 to protect and evangelize the platform when Oracle appeared to be losing interest in it. Starting in early 2016, a variety of different people in the community began to notice that work on EE 8 had stopped. Mailing list traffic abruptly ceased and few specification revisions were published. A community effort, which became the Java EE Guardians, was then made to document the lack of prod the various specifications. A website was constructed. On the website, the findings were published with the goal of alerting the larger community and also prodding Oracle to get the specifications moving forward again.
At JavaOne 2016 Oracle announced the reboot of Java EE 8 and the new standards they hoped to introduce in Java EE 9. The Java EE 9 proposals would finally embrace the cloud. Since JavaOne 2016, steady progress has been made on Java EE 8 with a target release of June 2017. With the reboot of Java EE, the Guardians have shifted their attention to educating the larger community about Java EE 8 and encouraging participation in the JCP. We are also encouraging vendors to adopt Java EE 8 fast and develop innovative solutions. Looking further ahead, we are paying close attention to Java EE 9 and advocating for the microprofile specification.
One of the challenges faced by the Java EE Guardians is that many Java developers don’t realize that they use Java EE every day. All of these are Java EE technologies:
- Web Services (JAX-RS/JAX-WS)
- JPA (Hibernate/Eclipselink)
- Web Sockets
- Container (Tomcat/Jetty/WebSphere/WebLogic/GlassFish/Payara)
Addressing this challenge requires evangelism: giving education and providing training.
To get involved, send an email to our Google Group (see below). You’ll be listed as a supporter of Java EE. You can also list your company and/or Java User Group affiliation. Once you are a member:
- Let others know about the Java EE Guardians
- Give Java EE Guardian presentations at your next local JUG meeting to meeting at work