Do you want to have a say in what happens for the next version of Jakarta EE? Check out the new edition of the Jakarta EE Survey 2022 by OmniFish, which follows the tradition of the bi-annual OmniFaces surveys. The purpose of the survey is to help everybody understand the current status of the Jakarta EE ecosystem, what we as a community represent, which parts of Jakarta EE we all use the most and what we all expect from Jakarta EE in the future.
We’d like to invite all Jakarta EE users to participate in the survey here:
You might also help spread the word about it so that the results are as relevant as possible. Tell your friends, share the survey on social media:
Jakarta EE 10 was released just a few weeks ago with a few interesting features. Several runtimes support it already. The work on Jakarta EE 11 is just starting. Now is the perfect time to look at the current Jakarta EE landscape, evaluate what the latest Jakarta EE brings, what is still missing, and what is more important for Jakarta EE users to focus on in the future. One of the best ways to do it is to collect opinions of Jakarta EE users directly, via a survey. Arjan Tijms, one of the OmniFish founders, has been doing that with the OmniFaces survey in the past few years and has always shared the results with the community with a commented analysis on the OmniFaces blog. You can have a look at the results of the previous surveys from 2020 and 2018.
The current Jakarta EE survey for the year 2022 is based on the questions from the previous OmniFaces surveys, which are slightly modified to reflect the changes since the latest survey.
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. We omitted less popular answers. 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 frequency of releases.
We’d like to collect as many responses as possible and then share them with the Jakarta EE community so that we all understand better what we use and need. We believe this greatly helps everybody in improving the Jakarta EE ecosystem. The results of the survey may have an important impact of what will be added in Jakarta EE 11 and also on the ecosystem around Jakarta EE, such as vendor-specific features in Jakarta EE runtimes or tooling around Jakarta EE.
Join us in this effort, participate in the 2022 Jakarta EE survey and share the survey with your friends and followers.