Thread by @bazlur_rahman

This Twitter thread is about @JakartaEE 10.

Quick recap: #JavaEE was renamed #Jakarta EE; it transitioned from JCP to Eclipse foundation. It opened the door to open governess, open compatibly testing (open TCK), and of course, open-source.

Follow the threads 🧵👇👇👇

@JakartaEE is an integral part of the Java ecosystem. 25-35% of java application runs on JakartaEE application servers, e.g. #WildFly, #JBoss EAP, #Payara, #WebSphere/#Liberty, #WebLogic etc.

👇

70-80% of java applications use JakartaEE APIs one way or another. e.g. Tomcat, Hibernate, ActiveMQ, Jetty, CXF, Jersey, RESTEasy, Quarkus, Microprofile, Spring. Dig a little deeper, and you will find @JakartaEE APIs.

👇

It’s a lively ecosystem; you have @JakartaEE 9, @MicroProfileIO, & Helidon. @QuarkusIO, introduced after @micronautfw & @helidon_project, remains a popular framework. Though JavaEE8 is still around, JakartaEE 9 is considered a foundation for innovation to drive new features
👇

@JakartaEE 9 moves all relevant specifications from javax to the Jakarta namespace. Unfortunately, that causes some breaking changes, but the migration rather seems easy. There are tools to do that. It also removes older deprecated technologies and moves Java 8 to Java 11.
👇

One of the most commonly used services in the Jakarta Concurrency API is the #ManagedExecutorService. It is similar to Java SE ExecutorService but in a @JakartaEE environment. Earlier, we had a vendor-specific setting to configure it. Now it can be defined with just annotation
👇

@Asynchronous
This used to be an EJB annotation, but the EJB one is a bit out of date. Also, in EJB, we can’t specify the thread pool. Now it comes with @JakartaEE 10, which doesn’t require using EJB, and we can specify the thread pool. So it can be used with any CDI bean.

👇

Bootstrap API:
If you are invoking a rest service outside of a @JakartaEE environment, e.g. unit tests, integration tests etc., this is good to have a standalone API to do that. With this, you don’t need to run the entire container.

Multipart/form-data

Every vendor used to support this in their specific way, but now we will have a standard way to deal with the multipart form submission.

#JakartaEE 10
👇

@JakartaEE 10 now brings a standard way to support OpenID Connect with the #OpenIdAuthenticationDefinition annotation.
Life is much simpler; specify the required properties, such as providerURI, clientId, clientSecret, redirect URI, etc., and that's it.

👇

@JakartaEE Persistence now supports UUID as a key. This is particularly important for the Cloud environment since many databases don’t automatically generate UUID. With this, we can create a UUID key from the Java side.

#JakartaEE10

👇

You can now write your UI code entirely in Java with the pure Java faces View. If you are particularly not interested in writing any tagging language whatsoever, you'll love it.

#JakartaEE10 #JakartaEE
👇

Now a bit about @jee_ambassadors: We are an independent grassroots group of people committed to moving Jakarta EE forward through active community participation and advocacy. If you want to join, and contribute, find out more here: jakartaee-ambassadors.io

👇

And finally, keep an eye here on my Twitter (follow?) to get more similar threads in the future.