Defining Jakarta EE 12 Scope in Program Plan: JMS

[Kito Mann]

From Reza's doc: https://docs.google.com/document/d/1U2qEqF9K969t5b3YuX4cwex5LJPvF3bt1w27cdKNpDM/edit?usp=sharing

Why 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 | @kit...@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.

[Kito Mann]

From Reza's doc: https://docs.google.com/document/d/1U2qEqF9K969t5b3YuX4cwex5LJPvF3bt1w27cdKNpDM/edit?usp=sharing

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.

+1 for this. There are way too many specs, and I think we should drop as many as possible, or at least start the process of doing so. 

___

Kito D. Mann | @kit...@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.

[Kito Mann]

From Reza's doc: https://docs.google.com/document/d/1U2qEqF9K969t5b3YuX4cwex5LJPvF3bt1w27cdKNpDM/edit?usp=sharing

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.

+1

I think this is key, and should be the case for every Jakarta EE release going forward. I think there really needs to be a gap analysis done of new features vs spec for each one. Perhaps that can be the goal for Jakarta EE 12 in addition to handling well-known issues like ensuring Records are usable everywhere. 

___

Kito D. Mann | @kit...@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.

On Oct 30, 2024 at 2:17 PM -0400, Kito Mann <kito...@virtua.tech>, wrote:

[Kito Mann]

This wasn't in Reza's document, but I'd like to also see a longer-term roadmap for Jakarta EE as part of Jakarta EE 12. Having some idea of what's going to happen in Jakarta EE 13, 14, and beyond (recognizing that it may change), is very important for the success of the project (and would avoid scenarios like this one, where there is no clear plan for the next release). Again, OpenJDK is a good example of this; it's clear what is being working on, although no one really knows exactly when/where a new feature will land. 

___

Kito D. Mann | @kit...@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.

On Oct 30, 2024 at 2:17 PM -0400, Kito Mann <kito...@virtua.tech>, wrote: