Jakarta EE Survey 2022

At OmniFaces we poll the community from time to time and again about Jakarta EE (previously Java EE) and related technologies.

With the transfer of Java EE to Jakarta EE now fully completed and Jakarta EE 10 released, people are now starting to think about Jakarta EE 11, the second Jakarta EE feature release. As such it's a good time to poll the community again. This year we're doing so in cooperation with OmniFish.

In the 2022 edition, there are 4 categories of questions again:

  • Current usage of Jakarta EE
  • Servlet containers
  • APIs related to Jakarta EE
  • The future of Jakarta EE

Compared to 2020, we simplified some of the questions once more; again omitting some of the less popular options to make it more manageable. We kept the questions about the future of Jakarta EE and MP together as this issue still isn't resolved. We also ask about the preferred Jakarta EE cadence. As Jakarta EE 10 is the first feature release, we haven't really established a cadence yet. EE 10 however was released 1 year and 4 months after Jakarta EE 9.1. The plan was for 1 year, but some issues with particularly the Concurrency TCK pushed it out.

Jakarta EE 10 is as mentioned the first feature release, and is generally well received, but in order to keep up the pace it's still very important that we know what matters to all of its users out there.

So therefor we'd like to invite all Jakarta EE users to participate in The Jakarta EE Survey 2022

Comments

Popular posts from this blog

Dynamic beans in CDI 2.0

Dynamically adding an interceptor to a build-in CDI bean

Should the community take over JSF.next or not?