The document discusses plans for Jakarta Messaging 3.x, which will serve as the basis for the JMS API in Jakarta EE 9 and beyond. It outlines the timeline of JMS specifications and their inclusion in Java EE and Jakarta EE. Ideas for Jakarta Messaging 3.x include incorporating unreleased features from JMS 2.1, improving support for CDI, adding property conversion and JSON-B message support, and developing a MessagingClient similar to MicroProfile Rest Client. The presentation encourages involvement in the Jakarta Messaging and sample code projects on GitHub.
3. @dblevins @tomitribe
JMS Timeline
May 2013
JAVA EE 7
JMS 2.0
JCA 1.6
Sep 2019
JAKARTA EE 8
JMS 2.0
JCA 1.7
Aug 2017
JAVA EE 8
JMS 2.0
JCA 1.7
JMS 2.1
Proposed
Sep 2013
JAVA EE 7
JMS 2.1
Withdrawn
Nov 2016
JAVA EE 7
4. @dblevins @tomitribe
JMS Timeline
Sep 2020
JAKARTA EE 9
3.0
javax > jakarta
2021
JAKARTA EE 10
3.1
new features
2021?
3.2
new features
….
3.3
new features
5. @dblevins @tomitribe
JMS Timeline
Sep 2020
JAKARTA EE 9
3.0
javax > jakarta
2021
JAKARTA EE 10
3.1
new features
2021?
3.2
new features
….
3.3
new features
48. @dblevins @tomitribe
Get Involved
Jakarta Messaging
- https://github.com/eclipse-ee4j/jms-api
- https://accounts.eclipse.org/mailing-list/jms-dev
This Code
- https://github.com/tomitribe/jms-proposals