Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jms-dev] Jakarta Messaging Plan for version 3.1 (Jakarta EE 10)
Hi all,

I noticed that Messaging didn't submit a plan for review for Jakarta EE 10. Do we still want to submit a plan so that we can deliver a new version of JMS in EE 10?

I think that plans should have been submitted by April 15 but we may still try to submit a plan because JMS is a very important Jakarta EE specification. It wouldn't be a good message if JMS didn't get any update for EE 10, at least with very minor updates.

Because we didn't have any discussion about new features recently, we could introduce something from the roadmap outlined by David in 2019 in a github issue. I would only go after things that are rather straightforward, long overdue, and already well documented. So from the items in that issue, I suggest to consider only:
  • Annotation-Based API for Consuming Messages #243
  • CDI Message Consumers #244
  • MessagingClient #249
Additionally, we can support repeatable annotations in some cases, e.g. for JMSDestinationDefinition.

What do you think? Do you want me to start working on a plan for Messaging 3.1 that we would submit to the https://github.com/jakartaee/specifications repository?

Should we plan to add the new features as I suggested above? Or it's much more that we can handle and it's better to submit a plan just to add fixes and possibly support repeatable annotations?

What do you think?

Ondro

Back to the top