| [jakarta.ee-community] Defining Jakarta EE 12 Scope in Program Plan: Deprecation |
Why does aggressive deprecation matter?
We can reinforce the market message that Jakarta EE intends to evolve by deprecating technologies and features that are out-of-date. Fortunately, Jakarta EE has done reasonably well in this regard and should continue to do so in Jakarta EE 12. For example, the Application Client Container could easily be deprecated and we can declare our intent to deprecate EJB.
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.