| [jakarta.ee-spec] Defining Jakarta EE 12 Scope in Program Plan: Java SE |
Why is adopting Java SE important?
Part of the success of the new Java SE release strategy is that developers are anticipating and looking forward to at least trying if not adopting new Java SE features. As a result, a Jakarta EE release that gets in the way of using the latest Java SE will likely lead to user disappointment. If we do not at least keep up with LTS releases, the perception of Jakarta EE being a technology that isn’t up-to-date or competitive persists. Specifically in terms of Records, it is very good that many Jakarta EE 11 specifications such as Persistence and Validation have adopted it. Disappointingly, Records were not adopted in the key use case of JSON Binding. We should work hard to ensure similar gaps do not happen in Jakarta EE 12.
From Reza's doc: https://docs.google.com/document/d/1U2qEqF9K969t5b3YuX4cwex5LJPvF3bt1w27cdKNpDM/edit?usp=sharingWhy does modernizing Messaging matter?JMS has been one of the key specifications in Java EE. It was virtually synonymous with messaging in Java for a long time. ... In past years, Kafka has largely replaced JMS for Cloud Native messaging. ... Messaging must be urgently modernized to address these problems.
I've been wondering about this for quite some time. Is it possible to extend JMS so that it works for Kafka and perhaps cloud message services? That would make it very relevant again. It looks like Spring Messaging handles Kafka.
___
Kito D. Mann | @kito99@mastodon.social | LinkedIn
Java Champion | Google Developer Expert Alumni
Expert consulting and training: Cloud architecture and modernization, Java/Jakarta EE, Web Components, Angular, Mobile Web
Virtua, Inc. | virtua.tech
+1 203-998-0403
* Enterprise development, front and back. Listen to Stackd Podcast.
* Speak at conferences? Check out SpeakerTrax.