Follow Java EE’s journey from J2EE 1.2 to what’s coming in Java EE 8 and see how it’s adapted from monoliths to microservices and the cloud.
In this article, you will find out about the history of the Java EE ecosystem: Where it came from and how it has changed over the last few decades. You will discover the major milestones in its development from J2EE 1.2 to its current incarnation Java EE 7 and we will peek into the future at what Java EE 8 has in store.
You will discover how to get involved with the development of the platform itself and how to join the JCP.org to make an even greater contribution. Find out about the Java EE Guardians and how you can support the development and growth of the platform.
It has its own contextually aware dependency injection framework at the heart of it programming model.
These technologies still exist in the Enterprise platform today but in a much more advanced and comprehensive form.
So what’s planned in Java EE 8?
Oracle is moving Java EE’s focus to microservices and the cloud, and the next version of Java EE is going to include APIs that complement this new direction.
So as well as advancements in some already established technologies such as Bean Validation, Context and Dependency Injection, JavaServer Faces, JAX-RS (RESTful web services) , JSON-Processing, and Servlets, there will be two new APIs.
JSON-binding, a dedicated security API and Security API for Java EE, designed to standardize security.
Java EE 9 will see even more APIs designed for the development of microservices and cloud-based applications.
The Java EE Guardians are an independent group of Java Enterprise Edition developers and evangelists that are collaborating to move Java EE forward.
Once a JSR is approved and its development finalized, it forms part for the next release of the platform.
