Welcome to issue number one hundred and eighty of Hashtag Jakarta EE!
In last week’s Hashtag Jakarta EE, I listed all specifications planning an update for Jakarta EE 11. Among these, three of them are currently not part of the Platform. These independent component specifications, Jakarta Data 1.0, Jakarta NoSQL 1.0, and Jakarta MVC 3.0, are all candidates for inclusion in Jakarta EE 11.
Jakarta Data provides an API to allow easy data access by implementing the Repository Pattern. Pretty much the way Spring Data does it. Join the discussion to voice your opinion regarding the inclusion of Jakarta Data in Jakarta EE 11.
Jakarta NoSQL provides a standard for streamlining the integration of Java applications with NoSQL databases. Join the discussion to voice your opinion regarding the inclusion of Jakarta NoSQL in Jakarta EE 11.
Jakarta MVC standardizes the action-based model-view-controller pattern as a complement to the component-based offered by Jakarta Faces. With the bubbling conversations about moving some of the rendering back to the server in the various client-side JavaScript frameworks, Jakarta MVC may turn out to be more relevant than ever. Join the discussion to voice your opinion regarding the inclusion of Jakarta MVC in Jakarta EE 11.
From time to time, some unexpected and/or cool usages of Jakarta EE specifications pop up. This week, Richard Schilling sent an email to the Jakarta EE Platform mailing list telling about his efforts to use Jakarta EE on Android. Check out jakartaee-mobile on GitHub.
If you are new to Jakarta EE or just want to complete a course for the Jakarta EE skill on LinkedIn, I have just published an overview course of Jakarta EE on LinkedIn Learning. Check it out, and tell me what you think!
