Jakarta EE Platform Call
Date: 2026-10-20
Present:
- Jared Anderson (IBM)
- Kyle Aure (IBM)
- John Clingan (IBM)
- Scott Marlow (IBM)
- James Perkins (IBM)
- Nathan Rauh (IBM)
- Arjan Tijms (OmniFish)
- Jan Westerkamp (iJUG)
- Ivar Grimstad (Eclipse Foundation)
- Michael Redlich (Garden State JUG)
- César Hernández (Tomitribe)
Top of mind for Jared, James
- CCRs
- 6 remaining from Payara, but they have issues
- Platform TCK call 11:00 ET on Wednesday
- Jakarta EE Community Open Call
OCX 2027
- CfP is open
- December 6 is the deadline
- Modern software development is the track to submit Jakarta EE talks to. Can do others as appropriate to any talks.
- Want to also showcase how applications are using the technology
Jakarta EE 12
- M8 week 4 of 6 starts this week (M8 ends November 15)
- Release review must start at the end of this milestone
- Core Profile progress
- Targeting 4Q 2026. JakartaOne is December 1
- To release Core profile November 30
- Components specs would need to start release review by Oct 30
- Core Profile release review start by Nov 13
- Need TCK updates for Core Profile
- Version updates
- Integration testing additions?
- Arjan will setup the CI jobs for running the TCK
- James will try to find time to look at the release jobs
- (EE4J Parent POM version 2.0.6)
- Core Profile implementation for ratification discussed
- Likely would be Glassfish
- Small possibility of a Wildfly preview / alpha release
- Annotations
- No traction for a 3.1 release.
- CDI
- 5.0 Final release is published
- JSON-B
- M2 PR is created
- Staged version of yasson passes the M2 TCK
- Yasson M2 will also be released
- 3.1.0 M1 Yasson is released. It passes the M1 TCK
- Will need JSON-P release before do final release of JSON-B
- JSON-P
- No M1 yet, but is planned
- Kyle trying to get committership with some PRs
- PRs are getting in, but no M1 yet
- Mark had issues with getting Jenkins build updates done. Getting that resolved
- REST
- Web Profile progress
- Authorization
- No API update yet in Jakarta
- Vote approved to move to Web Profile
- Need to update the spec and jakartaee api
- Servlet
- 6.2.0 M2 API was released around May
- The specification page still needs to be updated to reflect this version
- Pages
- 4.1.0 M2 API also release around May
- Tags
- 3.1.0 M2 API released in July
- Faces
- 5.0.0 M6 API released
- Glassfish vNext has faces updates in it
- Security
- 5.0.0 M2 API released in May
- Still need to rehome the API without “enterprise” in the group name
- Glassfish vNext has security updates in it
- Transaction
- Spec / API updates, but no milestone of the API yet.
- TCK move over from platform PR is there for them to accept
- Depends on some TCK shared libraries that would want to have an EE 12 TCK milestone release
- Concurrency
- 3.2.0 M3 API released last week
- IBM Liberty is working on implementation. It is the usual ratifying implementation
- Data
- 1.1.0 M4 API released
- Depends on Query releasing before can do final release
- Expression Language
- 6.1.0 M2 API released in May
- Persistence
- 4.0.0 M7 API released last month
- The specification page still needs to be updated to reflect this version
- Depends on Query releasing before can do final release
- The OmniFish folks are working on EclipseLink 6
- Discussion from the Persistence spec team about removing the duplicate TCK tests from the platform-tck.
- Query
- 1.0.0 M2 of the specification is available
- No API
- TCK covered by Data, NoSQL and Persistence
- Validation
- 4.0.0 M1 API released in October 2025
- WebSocket
- 2.3.0 M2 API released in January
- Open Forum
- MicroProfile updates
- Ballots are out for OpenTelemetry, OpenAPI, JWT Auth and MicroProfile Platform.
- Jakarta EE Future Directions Meeting
- October 29, 2026, 12:00 EDT
- Continuation of MicroProfile folding under Jakarta EE
- EclipseLink Update
- Robert Patrick from Oracle is also looking at the integrating and the implementation.
- NoSQL
- Is there a plan to still get this into Jakarta EE 12.
- There is no open ballot, but someone can raise the ballot.
- From the October 6 call:
- https://speakerdeck.com/otaviojava/jakarta-nosql-1-dot-1
- Otavio shared slides showing the current status of the NoSQL 1.1 API for application use. Communication API that was discussed previously and is now included in 1.1
- Previously discussed 1.2 function and that is in 1.1 now
- The API doesn’t depend on a configuration model. Only the implementation does