Re:What's New in Jakarta EE 10?
by latchkey on Wednesday September 14, 2022 @11:42AM
(#32838761)
As the co-founder of Apache Jakarta and first hearing about this Jakarta EE thing just now, which also seems Java (tm) related, it seems like a weird overlap in naming.
Re:What's New in Jakarta EE 10?
by bitwize on Wednesday September 14, 2022 @12:22PM
(#32839410)
Jakarta EE is Java EE. When Oracle bought Java they cut Java EE loose because Spring and Spring Boot were eating the world and Oracle didn't want to be in the business of maintaining the losing Java enterprise framework. But they couldn't call it Java EE anymore because Oracle holds the Java trademark.
Re:What's New in Jakarta EE 10?
by latchkey on Wednesday September 14, 2022 @12:16PM
(#32839307)
Oh interesting, thanks for this!
It is no wonder that they couldn't come up with a better name [0]. For anyone else wondering, we came up with that name because it was the name of the conference room that we met in at the Sun campus to discuss creating Apache Jakarta, because Sun was upset we were originally using Apache Java. As a 'gift' of appreciation for making a halfway decent servlet engine at the time (Apache JServ), they also gave us Apache Ant and... Tomcat. The rest is history...
I've also been long out of the Java ecosystem, so that xkcd is especially relevant. Let's go shopping!
Re:What's New in Jakarta EE 10?
by kaba0 on Wednesday September 14, 2022 @04:09PM
(#32842683)
Well, let’s add that the project didn’t want to continue with the “standard committee”-like model, so they quit on their own accord, not due to some malicious intent on Oracle’s part. But as a now outside entity it would indeed wouldn’t make sense to use the standard lib’s packages, so a change was necessary.
Re:What's New in Jakarta EE 10?
by latchkey on Wednesday September 14, 2022 @05:08PM
(#32843373)
No. Tomcat was created by James Davidson, who worked for Sun, and then heavily modified once it was over in Apache Jakarta.
I did a few contributions to the codebase (I wrote the first class reloader implementation), but was super busy with many other codebases at that point that I had started/created... Turbine, Velocity, Multiple Commons projects, etc.
Re:What's New in Jakarta EE 10?
by exabrial on Wednesday September 14, 2022 @12:33PM
(#32839583)
One aspect I don't want to see go away is "configuration goes in the app container"... basically, if you have a datasource, define it at the app container level, then the application just requests it by name, not caring what it's actually connecting to.
Happy to see acceleration of these API definitions. One thing I miss is having a "big picture" plan for all of EE APIs. It'd be really nice to have _Everything_ be defined as a CDI portable extension for instance.
Re:What's New in Jakarta EE 10?
by ysleepy on Wednesday September 14, 2022 @01:45PM
(#32840628)
I'm the opposite, can't wait for app containers to go away. Probably have their place but it's giving up control to some stateful black box. I always embed a jetty or something and do my own hikaricp.
Re:What's New in Jakarta EE 10?
by hsbauauvhabzb on Wednesday September 14, 2022 @03:59PM
(#32842558)
Every time I look at the Java ecosystem I feel lost. Versioning, package management, naming and ‘EE’ all seem to be ‘in the know’ things that keep outsiders outside.
Re:What's New in Jakarta EE 10?
by kaba0 on Wednesday September 14, 2022 @04:26PM
(#32842886)
I don’t think it is harder than any other ecosystem of similar size, it’s just unknown to you and feel different.
Jakarta EE is the old Java EE’s continuation, which is a huge standard for solving many kinds of complex business requirements (dependency injection mostly, with aspect-oriented programming). In a way it is a Spring alternative, but the truth is that Spring also uses several annotation of the standard so it more like building on top a subset of it. While it is a difficult topic, it is an ecosystem in its own right, so I don’t think it is meaningful to discuss it with Java itself — one can make a whole career as a java dev without touching it.
Package management is basically either maven or gradle, but both use the same registry for the most part, so on the surface level they both are quite easy to use.
I would guess you mean java’s versioning (eg. 8, 17, etc) - this couldn’t be easier, it’s just an integer that increases every 6 months. That is, for OpenJDK. This is the JVM-implementation, being both the reference and the most often used one. It has several forks that you might have heard of, but they share more than they differ. Some of these forks/vendors provide LTS-releases and this usually targets 8, 11, 17, 11+6k versions. That’s pretty much it.
In the meanwhile you literally have to use a tool to generate a base repo to write anything more complex than hello world in the JS ecosystem :D
Re:What's New in Jakarta EE 10?
by nerdponx on Wednesday September 14, 2022 @04:20PM
(#32842801)
I feel this way too. Clojure looks awesome. Kotlin looks nice. People tell me that even Java is pretty good now. There are a lot of JVM libraries and people say that the JVM itself is an engineering marvel.
But... the ecosystem is incredibly intimidating and there is no obvious starting point for a beginner. I know that with Clojure you can probably just stick to "Clojure stuff" like deps.edn, but that's also not really why people choose Clojure in the first place, nor does it seem like a sensible path to competency.
And I say this as a Python professional and a Common Lisp and Scheme hobbyist. My personal tolerance for chaotic and/or offbeat tooling ecosystems is high.
Re:What's New in Jakarta EE 10?
by mypalmike on Wednesday September 14, 2022 @07:37PM
(#32844988)
> there is no obvious starting point for a beginner
I think maybe some of this perception comes from the days when Java EE (Enterprise Edition) was very common. I worked on Java apps for many years and was fortunate to mostly avoid projects centered on Java EE.
For getting started with current Java development, you can download OpenJDK AND IntelliJ IDE. Then Google search for a tutorial on what you want to build (a command line tool is a good place to start, then maybe a web app if you're familiar with that domain). Start with just the Java language and then add Kotlin, Clojure, etc later when you are more familiar with the ecosystem - these languages add incidental complexity that you'll want to avoid as a beginner. I'd recommend Gradle for building. You'll see Maven mentioned. Avoid the tool but understand that "Maven repo" and similar terms refer to artifact repositories for downloading 3rd party libraries.
Re:What's New in Jakarta EE 10?
by kaba0 on Thursday September 15, 2022 @05:02AM
(#32849107)
Hell, probably intellij idea is enough - it will give you a drop down list of JDKs to choose from, and it will download it automatically/change it for a given project.
Re:What's New in Jakarta EE 10?
by kjeetgill on Wednesday September 14, 2022 @06:00PM
(#32844018)
Hmmm, I guess I find it straight forward enough. How can I help?
They've simplified it a ton lately. There's no real JRE vs JDK seperation any more. The Java Language / JVM versions are the same. Version 19 is just out and they release a version every 6 months now.
Any other languages like Clojure or Kotlin will have their own language versions and might specify a range of Java versions they work with.
You can think of Jakarta EE as just a version of some library that won't be relevant to you unless you use it. Like versions of react or angular or something.
Re:What's New in Jakarta EE 10?
by jackee10 on Wednesday September 14, 2022 @08:59PM
(#32845653)
I'm surprised that Jakarta EE (previously Java EE) still exists. We used to heavily use Java EE like maybe 10-12 years back, but it was such a mammoth that running those application servers, developing those EJBs and other things made application development such a heavy duty exercise. The only thing I liked was the Servlets API which was/is well designed and very lean to work with.
For us, it was good that Oracle stopped being invovled with Java EE. That allowed us to convince others in our team to move on to much simpler application development using core Java.
I had stopped paying attention to this Java EE/Jakarta EE area after the unnecessary drama that ensued in the community lead by an ex-Oracle employee.
I'm really surprised that Jakarta EE is still a thing.
Re:What's New in Jakarta EE 10?
by hyperman1 on Thursday September 15, 2022 @03:43AM
(#32848531)
I happened to reread part of an original EJB book, and with hindsight I am now wondering if EJB = microservice was the intended use. The app server would, on multiple machines, start and stop EJB instances like kubernetes does with node instances. The whole thing tries to hide there is a network in there, automagically connecting everywhere.
Which would make the whole bloat thing moot and the whole EJB stack comically misused.
But look at it as an EJB providing an interface to the outside world. Forget about making almost every class an EJB. Then the 2 styles start to look quite similar, especially if 'the network is the computer'.
There were of course still plenty of bad design decisions. Every vendor has its own RMI variant, requiring drivers instead of a standardized http+json. 4 files for the interfacevis iver the top. The EJB database interface was bad.
Re:What's New in Jakarta EE 10?
by kaba0 on Thursday September 15, 2022 @05:20AM
(#32849215)
Yeah, I did say that Java EE is kubernetes before it was cool :D
Actually, in a way it is sort of sad how unfamiliar we are of the “previous generation’s” solutions. It’s not like load balancing, zero downtime, RPC and scaling are new things.
Re:What's New in Jakarta EE 10?
by jackee10 on Wednesday September 14, 2022 @09:40PM
(#32845964)
After writing this comment and reading some others, I was reminded of CDI - the dependency injection blackbox. It was advertised as the next best thing to allowing developers to focus only on their business logic and let the CDI runtime inject the dependencies. That turned out to be giant mess. Couldn't understand what a piece of code was doing statically and you had to run the code, attach a debugger to find out what dependency got injected and what its implementation looks like. And of course, things behaved differently because some other dependency implementation got picked up and injected instead of the one that you had debugged in dev environment.
Simple code turned into a complete dependency injection spagetti just beacuse CDI was a specification and advertised as the next best thing to come from the Java EE ecosystem.
Re:What's New in Jakarta EE 10?
by bee_rider on Wednesday September 14, 2022 @12:42PM
(#32839697)
I disagree. A "what's new in <X>" post shouldn't describe what <X> is. Most of the people interested in updates on <X> will already know what it is, so adding that information to every article would be redundant.
They helpfully link to the jakarta.ee site which has an about page.
Re:What's New in Jakarta EE 10?
by throw_m239339 on Wednesday September 14, 2022 @03:30PM
(#32842121)
Java EE is basically a collection of API that are shared accross different Java web servers. It's a spec so basically you develop your java app on say glassfish server and you can deploy it on websphere, the servers holds all the libraries you need to run your app, so you can just deploy some small java zip file.
Because of trademark issues with Oracle around the name Java, the open source community had to rename all its API jakarta instead of java which is completely stupid and is a demonstration that Oracle is just here to milk the name Java.
Re:What's New in Jakarta EE 10?
by whartung on Wednesday September 14, 2022 @05:40PM
(#32843770)
Oracle open sourced and released the bulk of the Java Enterprise Edition specifications and source code.
But what they did not do, is release the Java trademark. So, the whole kit had to be called something else (in this case they chose Jakarta, which has history in the Java community and lets the colloquial "JEE" still work).
Part of this process what they had to rename ALL of the Java EE packages from the original "javax" root name to something else, again, in this case, "jakarta".
This has been a several year process that's held up a lot of advancement in the platform as it transitioned out of Oracle and over the Eclipse foundation.
At this point with moving to Java 11 and supporting Java 17 (no small feat), and having all of the packages renamed, repackaged, re-released, Jakarata EE is probably "finally free" from where it was back in "Java EE 8".
Re:What's New in Jakarta EE 10?
by exabrial on Wednesday September 14, 2022 @12:55PM
(#32839913)
Jakarta EE is all of the Java EE spec that are now open sourced. Right now in Java-land, the big development ecosystems are Quarkus, Spring Framework, and Jakarata EE. Jakarta EE's big advantage is CDI, which is a very nice dependency injection container and allows applications to be broken down and composed into easily testable modules. Quarkus partially implements CDI and has its own set of APIs. Spring has their own DI container that is showing it's age, but is still quite popular.
Re:What's New in Jakarta EE 10?
by gavinray on Wednesday September 14, 2022 @01:39PM
(#32840561)
Quarkus is Jakarta EE compatible (MicroProfile), for the subset of Java/Jakarta EE that it implements. That's largely the appeal.
The most recent release of JEE has a new "Core" profile, which is stripped down to bare minimum for AoT-compilation
and small memory footprint and implements CDI 4.0 Lite (based on Quarkus' "ARC" implementation)
Re:What's New in Jakarta EE 10?
by zokier on Wednesday September 14, 2022 @01:15PM
(#32840193)
Quarkus is "just" a Microprofile implementation. And Microprofile is largely evolution of JavaEE. Spring might have been a breath of fresh air in the JavaEE 6-7 days but I feel it has been since been leapfrogged by JavaEE/MP
Re:What's New in Jakarta EE 10?
by whartung on Wednesday September 14, 2022 @05:35PM
(#32843712)
Jakarta EE has several profiles, each focusing on different subsets of the overall EE platform. Web Profile is one of those subsets that focuses on the Web aspects of Jakarta EE. For example, Tomcat is more of a Web Profile stack (I don't know it Tomcat officially supports it or not) compared to the full boat EE containers like Glassfish, Websphere, etc.
Jakarta Concurrency (which is essentially portable access to container managed thread pools and other similar resources) was originally part of the full EE specification. Now they've moved it to the Web Profile so it can be used in those containers that do not support the entirety of Jakarta EE.
Re:What's New in Jakarta EE 10?
by TedDoesntTalk on Wednesday September 14, 2022 @07:24PM
(#32844868)
I understand but thought concurrency was larger than “web component “. I guess in the context of EE, it is not and I’m confusing it with java.util.concurrent
relevant: https://xkcd.com/1053/
It is no wonder that they couldn't come up with a better name [0]. For anyone else wondering, we came up with that name because it was the name of the conference room that we met in at the Sun campus to discuss creating Apache Jakarta, because Sun was upset we were originally using Apache Java. As a 'gift' of appreciation for making a halfway decent servlet engine at the time (Apache JServ), they also gave us Apache Ant and... Tomcat. The rest is history...
I've also been long out of the Java ecosystem, so that xkcd is especially relevant. Let's go shopping!
[0] https://twitter.com/codinghorror/status/506010907021828096 (this keeps coming up for me recently for some reason)
I did a few contributions to the codebase (I wrote the first class reloader implementation), but was super busy with many other codebases at that point that I had started/created... Turbine, Velocity, Multiple Commons projects, etc.
Happy to see acceleration of these API definitions. One thing I miss is having a "big picture" plan for all of EE APIs. It'd be really nice to have _Everything_ be defined as a CDI portable extension for instance.
Jakarta EE is the old Java EE’s continuation, which is a huge standard for solving many kinds of complex business requirements (dependency injection mostly, with aspect-oriented programming). In a way it is a Spring alternative, but the truth is that Spring also uses several annotation of the standard so it more like building on top a subset of it. While it is a difficult topic, it is an ecosystem in its own right, so I don’t think it is meaningful to discuss it with Java itself — one can make a whole career as a java dev without touching it.
Package management is basically either maven or gradle, but both use the same registry for the most part, so on the surface level they both are quite easy to use.
I would guess you mean java’s versioning (eg. 8, 17, etc) - this couldn’t be easier, it’s just an integer that increases every 6 months. That is, for OpenJDK. This is the JVM-implementation, being both the reference and the most often used one. It has several forks that you might have heard of, but they share more than they differ. Some of these forks/vendors provide LTS-releases and this usually targets 8, 11, 17, 11+6k versions. That’s pretty much it.
In the meanwhile you literally have to use a tool to generate a base repo to write anything more complex than hello world in the JS ecosystem :D
But... the ecosystem is incredibly intimidating and there is no obvious starting point for a beginner. I know that with Clojure you can probably just stick to "Clojure stuff" like deps.edn, but that's also not really why people choose Clojure in the first place, nor does it seem like a sensible path to competency.
And I say this as a Python professional and a Common Lisp and Scheme hobbyist. My personal tolerance for chaotic and/or offbeat tooling ecosystems is high.
I think maybe some of this perception comes from the days when Java EE (Enterprise Edition) was very common. I worked on Java apps for many years and was fortunate to mostly avoid projects centered on Java EE.
For getting started with current Java development, you can download OpenJDK AND IntelliJ IDE. Then Google search for a tutorial on what you want to build (a command line tool is a good place to start, then maybe a web app if you're familiar with that domain). Start with just the Java language and then add Kotlin, Clojure, etc later when you are more familiar with the ecosystem - these languages add incidental complexity that you'll want to avoid as a beginner. I'd recommend Gradle for building. You'll see Maven mentioned. Avoid the tool but understand that "Maven repo" and similar terms refer to artifact repositories for downloading 3rd party libraries.
They've simplified it a ton lately. There's no real JRE vs JDK seperation any more. The Java Language / JVM versions are the same. Version 19 is just out and they release a version every 6 months now.
Any other languages like Clojure or Kotlin will have their own language versions and might specify a range of Java versions they work with.
You can think of Jakarta EE as just a version of some library that won't be relevant to you unless you use it. Like versions of react or angular or something.
For us, it was good that Oracle stopped being invovled with Java EE. That allowed us to convince others in our team to move on to much simpler application development using core Java.
I had stopped paying attention to this Java EE/Jakarta EE area after the unnecessary drama that ensued in the community lead by an ex-Oracle employee.
I'm really surprised that Jakarta EE is still a thing.
Which would make the whole bloat thing moot and the whole EJB stack comically misused.
But look at it as an EJB providing an interface to the outside world. Forget about making almost every class an EJB. Then the 2 styles start to look quite similar, especially if 'the network is the computer'.
There were of course still plenty of bad design decisions. Every vendor has its own RMI variant, requiring drivers instead of a standardized http+json. 4 files for the interfacevis iver the top. The EJB database interface was bad.
Actually, in a way it is sort of sad how unfamiliar we are of the “previous generation’s” solutions. It’s not like load balancing, zero downtime, RPC and scaling are new things.
Simple code turned into a complete dependency injection spagetti just beacuse CDI was a specification and advertised as the next best thing to come from the Java EE ecosystem.
I am really glad we moved away from that area.
Something something java ?
They helpfully link to the jakarta.ee site which has an about page.
Because of trademark issues with Oracle around the name Java, the open source community had to rename all its API jakarta instead of java which is completely stupid and is a demonstration that Oracle is just here to milk the name Java.
But what they did not do, is release the Java trademark. So, the whole kit had to be called something else (in this case they chose Jakarta, which has history in the Java community and lets the colloquial "JEE" still work).
Part of this process what they had to rename ALL of the Java EE packages from the original "javax" root name to something else, again, in this case, "jakarta".
This has been a several year process that's held up a lot of advancement in the platform as it transitioned out of Oracle and over the Eclipse foundation.
At this point with moving to Java 11 and supporting Java 17 (no small feat), and having all of the packages renamed, repackaged, re-released, Jakarata EE is probably "finally free" from where it was back in "Java EE 8".
The most recent release of JEE has a new "Core" profile, which is stripped down to bare minimum for AoT-compilation and small memory footprint and implements CDI 4.0 Lite (based on Quarkus' "ARC" implementation)
https://jakarta.ee/specifications/coreprofile/10/
Why?
Jakarta Concurrency (which is essentially portable access to container managed thread pools and other similar resources) was originally part of the full EE specification. Now they've moved it to the Web Profile so it can be used in those containers that do not support the entirety of Jakarta EE.