Jakarta EE Platform Call

Date: 2026-05–05

Present:

• Jared Anderson (IBM)
• Kyle Aure (IBM)
• Scott Marlow (IBM)
• Chithra Mini (IBM)
• Anand N K (IBM)
• James Perkins (IBM)
• Matej Novotny (IBM)
• Nathan Rauh (IBM)
• Brian Stansberry (IBM)
• Reshmi Vijayan (IBM)
• Tom Watson (IBM)
• Michael Redlich (Garden State JUG)
• Jan Westerkamp (iJUG)
• Kenji Kazumura (Fujitsu)
• Ivar Grimstad (Eclipse Foundation)
• Cesar Hernández (Tomitribe)

Top of mind for Jared, James

• No new CCRs this week
• Jakarta Futures call last week going over REST 5.0 design thoughts I thought was productive. Flushed out a few thoughts about moving forward.
  • PR is located here
  • Main discussion has been about CDI injection into resource methods and knowing which fields are CDI injection and which is the Entity from the message body
  • Thought has been in 5.0 not allow general CDI bean injection into resource methods and anything that is not a known type is assumed to be the Entity from the message body
  • In 6.0 allow general CDI bean injection
  • OR rip off the bandaid and allow it in 5.0 and require everyone to change
• James out last week of May and first week of June
• Jared out last week of May as well
• Ivar will run the meeting on May 26 if people show up

Jakarta EE 12

• M4 week 6 of 6.5 starts this week (M4 ends May 15)
  • Goals to be in M4 if possible
    • REST 5.0 M1 API / spec
    • CDI 5.0 Milestone / Beta (currently at Alpha6)
      • Looking at doing a beta / milestone release since nearing completion of API and TCK changes
      • Found that when doing publishing from staging to maven that some artifacts were not promoted when there was more than just the standard expected artifacts. There are fixes for that that need to get added to the parent project with a new version of the plugin.
      • Link to the conversation is here
    • JSON-P 2.2 M1 API / spec
    • JSON-B 3.1 M1 API / spec
      • API and spec work has been mostly done for both JSON technologies
      • Updating to add new TCK tests
      • Need to update pipelines in order make a release
    • Security 5.0 M2 API / spec / TCK
      • Release PR is here
    • Faces 5.0 M2 API / spec / TCK
• Container Managed Resource Definitions discussion on mailing list
  • Aligns somewhat with issue 1105 and issue 1054
  • There are complications for things like connection management with shareability, security information. Other resource types do not have these issues
  • Jakarta Config would be a great solution for some of this, but that is currently not in plan for EE 12
  • If we did some of the changes outlined in the email, it could be a step in the wrong direction if we want Jakarta Config to be our end solution
  • ACTION: reply to the email with a link to the minutes from the meeting
• Jakarta NoSQL
  • Given the less tight schedule for EE 12, Otavio considers merging 1.2 into 1.1 to be a stronger candidate for inclusion
• Go through the issues labeled with EE12 in the issue tracker and update the status
  • Platform: https://github.com/jakartaee/platform/issues?q=state%3Aopen%20label%3AEE12
  • TCK: https://github.com/jakartaee/platform-tck/issues?q=is%3Aissue%20state%3Aopen%20label%3A12.0
  • Transaction read-only issue has been resolved and PR is merged so that connectors spec can move forward with implementing what needs to happen in connectors for 1201
    • Will need updates to platform spec for read only for datasources / JDBC, etc.
  • Persistence team may have updated language for 1135
    • https://github.com/jakartaee/persistence/issues/927
    • https://github.com/jakartaee/persistence/pull/932
  • Issue 1038 Http 3
    • Java 26 adds Http 3.0 client support
      • https://inside.java/2025/10/22/http3-support/
      • https://openjdk.org/jeps/517
• Platform TCK 10.0.7
  • https://github.com/jakartaee/specifications/pull/900
• Platform TCK 11.0.3
  • Should wrap up soon
  • Still pending changes that will go into 11.0.4
• MicroProfile 7.2
  • Plan review ballot passed