Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [messaging-dev] Update Jakarta Messaging 3.1 page


The sentence about draft should be removed, it's just an oversight that it wasn't deleted in the release review PR.

However, as Reza wrote, the specification has been rather dormant. There was some activity more than a year ago, which led to a common vision of the future of the Messaging spec. But it hasn't been followed up. I wanted to coordinate this effort but didn't have enough time for that, I only managed to release what other people contributed to the 3.1 version (although it wasn't much). Since then, I've left Payara, co-founded OmniFish, and, sadly, I now have even less time for working on the Messaging spec. So I don't plan putting much effort into it in the foreseeable future..

All the best,
Ondro Mihalyi

Director, Jakarta EE expert
OmniFish - Jakarta EE Consulting & Support |
Omnifish OÜ, Narva mnt 5, 10117 Tallinn, Estonia | VAT: EE102487932

On Mon, Sep 5, 2022 at 2:35 PM reza_rahman@xxxxxxxxx <reza_rahman@xxxxxxxxx> wrote:
I have not seen any serious work on this mailing list for a very long time. I hope you get some useful input. My suggestion is to treat it as a dormant project and do what you can to move things forward. I think the folks from the Eclipse Foundation could help.

Unfortunately Microsoft does not currently have the mandate to contribute to this particular project too directly just yet. That could easily change with some substantive interest in evolving the project from its current committers, for example towards cloud focused modernization or even general API/usability improvements.

I did create an issue triage some time ago: It was discussed briefly but I don’t think followed up on much.

From: messaging-dev <messaging-dev-bounces@xxxxxxxxxxx> on behalf of Jean-Louis Monteiro <jlmonteiro@xxxxxxxxxxxxx>
Sent: Monday, September 5, 2022 6:18 AM
To: messaging-dev@xxxxxxxxxxx <messaging-dev@xxxxxxxxxxx>
Subject: [messaging-dev] Update Jakarta Messaging 3.1 page
Hello team,

The specification committee asked me to follow up with you in order to get the Jakarta Messaging 3.1 page updated.

It's still showing Draft even though the ballot is completed. We don't need to re-ballot, but it would be great to PR the project to perform some updates.

A lot of projects have been able to extract the TCK from the Jakarta Platform project. Did you end up doing it also? It looks like no, but we would need a confirmation and probably make it clear on the summary page. If so, please make sure to also create an issue to fix it for the maintenance release. If it was done, it definitely needs to be added.

From the change log, it looks like aside from some minor changes, it was mainly clean up. A while back, there were a lot of ideas and interest in getting the specification updated and simplified. Is it something still planned or being discussed?

Can you guys acknowledge the request and tell me if that is possible or not?
Also, if you guys need some help, I'm available to help as much as I can. For instance, I can do the boiler plate to create the PR, but I would at least need the input.

Thank you all.
messaging-dev mailing list
To unsubscribe from this list, visit

Back to the top