[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakarta.ee-spec] Defining Jakarta EE 12 Scope in Program Plan: Roadmap
|
100% in agreement. This is something I intend to discuss starting
in the Steering Committee (which according to the Working Group
charter is actually responsible for roadmaps:
https://www.eclipse.org/org/workinggroups/jakarta_ee_charter.php)
once the dust settles on the 2025 Program Plan and it's clearer
that there is a recognizable outline for Jakarta EE 12 including
delivery date, Java SE version support, and big ticket items
(hopefully replacing most of EJB, modernized configuration,
modernized Messaging, deprecations).
On 10/30/2024 2:29 PM, Kito Mann wrote:
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.
On Oct 30, 2024 at 2:17 PM -0400,
Kito Mann
<kito.mann@xxxxxxxxxxx>, wrote:
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.