The most popular Java EE 7 technologies according to ZEEF users

-
For some time now I'm keeping a page at ZEEF.com about Java EE 7. The page covers pretty much all Java EE 7 technologies, so the amount of clicks on the links of this page may give some indication of what parts of Java EE 7 are most popular with users.

At the moment of writing the top 20 list for the last 8 weeks looks as follows:

Position Link Category
1 Beginning Java EE 7 by Antonio Goncalves Java EE 7 overal
2 The Java EE 7 Tutorial Java EE 7 overal
3 Java EE 7 Essentials by Arun Gupta Java EE 7 overal
4 Java EE 7 code samples Java EE 7 overal
5 What's New in JAX-RS 2.0? (2) JAX-RS 2.0
6 Java EE 7: And Then What? Java EE 7 overal
7 JSF 2.2 new features in context [slides] JSF 2.2
8 CDI 1.1 available :-) CDI 1.1
9 Java EE 7 support in Eclipse 4.3 Java EE 7 overal
10 JSF 2.2: HTML5 friendly markup JSF 2.2
11 A closer look at the JSF 2.2 View Action JSF 2.2
12 What's new in JSF 2.2? JSF 2.2
13 Getting Started with JSON-P Java API for JSON Processing (JSON-P) 1.0
14 JSF 2.2 and HTML5 JSF 2.2
15 An overview of batch processing in Java EE 7 Batch Applications for Java Platform 1.0
16 Method validation in Bean Validation 1.1 Bean Validation 1.1
17 What's new in EJB 3.2 ? EJB 3.2
18 Java EE 7 Delivers Expression Language Enhancements Expression Language 3.0
19 Injecting An ExecutorService With Java EE 7 Concurrency utils for Java EE
20 What's new in Java EE 7's authentication support? JASPIC 1.1

As can be seen the general Java EE 7 topics are by far the most popular. There may be multiple explanations for this though. Is it simply the fact that the block containing the Java EE 7 links is the top left one (which people thus typically see first), or the fact that the page's title is "Java EE 7", so it primarily attracts people looking for general Java EE 7 stuff? Or is it indicative that people are increasingly seeing Java EE 7 as a single platform instead of a mere collection of individual specs?

After Java EE 7, a link about what's new in JAX-RS 2.0 was the most popular one, closely followed by links about JSF 2.2 and CDI 1.1. Aggregated on total clicks per category (not shown in the table) JSF 2.2 was the most popular category after Java EE 7.

With some distance we see JSON-P, JBatch, Bean Validation 1.1, EJB 3.2, EL 3.0, Concurrency utils for Java EE and JASPIC 1.1. Remarkable is that JPA 2.1, JMS 2.0, Servlet 3.1 and WebSocket didn't make it into the top 20 list for the last 8 weeks. Also remarkable is that JASPIC 1.1, which normally doesn't seem to be that well known among users, just barely makes it into the top 20 of most popular links.

Ordered by the highest ranking single link, the most popular Java EE 7 technologies according to ZEEF users thus seem to be the following:

  1. Java EE 7 overal
  2. JAX-RS 2.0
  3. JSF 2.2
  4. CDI 1.1
  5. JSON-P
  6. JBatch
  7. Bean Validation 1.1
  8. EJB 3.2
  9. EL 3.0
  10. Concurrency utils for Java EE
  11. JASPIC 1.1

Conclusion

We can't draw too many conclusions from this list, as the location of the link blocks on the page, the position of the links within each block, as well as the titles of the posted links play a role as well. As I'm active in the JSF community and not in say the JPA one, there may be some bias for JSF as well. Still, the page has a diverse amount of links, a diverse amount of referrals and there were a few thousand visitors over the last 8 weeks so I hope the data gives us at least some insight.

Arjan Tijms

Comments

Post a Comment

Popular posts from this blog

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 cade
Read more

Implementing container authentication in Java EE with JASPIC

-
This article takes a look at the state of security support in Java EE 6, with a focus on applications that wish to do their own authentication and the usage of the JASPI/JASPIC/JSR 196 API. Update: the further reading section has been moved to my ZEEF page about JASPIC . This contains links to articles, background, questions and answers, and more.   Declarative security is easy In Java EE it has always been relatively straightforward to specify to which resources security constraints should be applied. For web resources (Servlets, JSP pages, etc) there is the <security-constraint> element in web.xml, while for EJB beans there's the @RolesAllowed annotation. Via this so called 'declarative security' the programmer can specify that only a user having the given roles is allowed access to the protected web resource, or may invoke methods on the protected bean. The declarative model has a programmatic counterpart via methods like HttpServletRequest#isUserInR
Read more

Counting the rows returned from a JPA query

-
Despite being almost ten years old, the JPA specification to this day has rather poor support for basic paging/sorting/filtering. Paging/sorting/filtering is used in a lot of (CRUD) applications where the result from a query is shown in a table, and where the user can scroll through the results one page at a time, and where this result can be sorted by clicking on any of the table column headers. In order to support this a number of things are generally needed: The total number of rows (or entities) in the full result must be known There should be support for an offset in the full result and a limit for the amount of rows that will be obtained The column (attribute) on which to sort must be dynamically added to the query Search expressions must be dynamically added to the query As it appears, only offset/limit is directly supported in JPA. A sorting column can only be added dynamically when using the overly verbose and hard to work with Criteria API. Search expressions
Read more