On the 10th of September it finally happened: the day the community had been waiting for, finally arrived. The Eclipse Foundation has released Jakarta EE 8, the first official release of the Java EE successor, almost two years after the birth of the Eclipse EE4J Project. Christian Kaltepoth will keep up us up to date with his new column “EE Insights”, and will provide us with insider-knowledge of the Jakarta EE universe.
What a week this has been for Java! Jakarta EE 8 and JavaFX 13 are already here, and Java 13 is waiting in the wings for its moment to shine! Now that the dust has settled a little bit and we got some sleep after the Jakarta One online conference, we’ve put together a little something about the release of Jakarta EE 8.
To celebrate the long-awaited release of Jakarta EE 8, we’re featuring content from prominent names and faces in the world of Jakarta EE and enterprise Java. This article is written by Eclipse Foundation Jakarta EE Program Manager Tanja Obradovic.
To celebrate the long-awaited release of Jakarta EE 8, we’re featuring content from prominent names and faces in the world of Jakarta EE and enterprise Java. This article is written by Arjan Tijms.
After what seemed like eternity, the time has finally come – the long awaited first release of Jakarta EE is now officially in the hands of the public. Now the community can start hoping for faster development of the platform.
Jakarta EE 8 is finally here! It heralds a new era for Enterprise Java, as finally the community can look forward to the platform’s faster development. To celebrate, we sat down with Executive Director of the Eclipse Foundation, Mike Milinkovich to talk about the first release of Java EE under the umbrella of the Eclipse Foundation.
A discussion that could be critical to the future of Jakarta EE and Eclipse MicroProfile is taking place right now. What exactly should the relationship be between the two? We’re past the idea of MicroProfile as an incubator, but pinning down what the future will look like is surprisingly difficult.
Following the JCrete unconference where a group got to brainstorming about the future of Jakarta EE and MicroProfile, Sebastian Daschner wrote a proposal as to how this relationship would look. We caught up with him and asked him some questions.
Every Monday, we take a step back and look at all the cool stuff that went down during the previous week. Last week, we published a new double issue of JAX Magazine, interviewed Red Hat’s Martin Klaus, learned about Jakarta EE 8’s release date, and lots more. Let’s have a look.
It’s been almost two years since it was announced that Java EE would be moving to the Eclipse Foundation with a new name: Jakarta EE. And now, at last, we have an expected release date for the first version under the Eclipse Foundation’s banner, Jakarta EE 8. And what else is happening in the world of Enterprise Java? Let’s find out.
Java EE 8 introduced a new API called the Java EE Security API (see JSR 375) or “EE Security” in short. This new API, perhaps unsurprisingly given its name, deals with security in Java EE. Security in Java EE is obviously not a new thing though, and in various ways it has been part of the platform since its inception. So what is exactly the difference between EE Security and the existing security facilities in Java EE? In this article we’ll take a look at that exact question.
According to the latest development in the negotiations between Oracle and the Eclipse Foundation, Jakarta EE will have to face certain restrictions surrounding the javax namespace. We caught up with Tanja Obradovic and talked about some of the most burning questions around the future of Jakarta EE.
What’s going on with Jakarta EE? Since the opening up of the Java EE, the switch from Oracle to The Eclipse Foundation has been underway. The latest news explains what is happening regarding the negotiation process, including the inability to come to an agreement regarding trademarks.
So many options, so little time. How can developers choose between Java EE, Jakarta EE, and Eclipse Microprofile? In this article, Sebastian Daschner goes over the options and explains why a mix of all three is the best of all worlds for resilient, cloud-native apps.