Skip to main content

Jakarta EE Platform Project

Home for the Jakarta EE Platform Team

Jakarta EE Platform Call

Date: 2026-04–14

Present:

  • Jared Anderson (IBM)
  • John Clingan (IBM)
  • Anija K A (IBM)
  • Scott Marlow (IBM) - will be 10 minutes late
  • James Perkins (IBM)
  • Nathan Rauh (IBM)
  • Brian Stansberry (IBM) (1/2 hour late)
  • Tom Watson (IBM)
  • Ivar Grimstad (Eclipse Foundation)
  • Michael Redlich (Garden State JUG)
  • César Hernández (Tomitribe)
  • Jan Westerkamp (iJUG)

Top of mind for Jared, James

Jakarta EE 12

  • M4 week 3 of 6 starts this week
  • Data 1.1 M3 API, TCK and spec released to maven central
    • jakarta.ee/specficiations/data/1.1 is not updated to reference M3 yet
      • Otavio will make a PR today
    • Should jakarta.data-stateful be jakarta.data.stateful-api?
      • Something to consider for M4.
      • Data team will get an issue open
  • Jakarta XML Binding 4.1 Plan review requested
    • Stand-alone spec that isn’t part of the platform any more
    • Plan is to provide EE 12 support and align with EE 12 goals
  • Moving Authorization to Web Profile discussion
    • Completely forgot to start discussion on mailing list
  • Need to update the milestone schedule to adjust for the changes discussed previous weeks
    • M4 Apr 1 to May 15
      • REST 5.0 M1 API / spec
      • CDI 5.0 Milestone / Beta (currently at Alpha4)
      • JSON-P 2.2 M1 API / spec
      • JSON-B 3.1 M1 API / spec
    • M5 May 16 to Jun 30
    • M6 Jul 1 to Aug 15
    • M7 Aug 15 to Sep 30 – ideally we release Core profile here or soon after
    • M8 Oct 1 to Nov 15
    • M9 Jan 1 to Feb 15, 2027 – Finalize all other specifications
    • M10 Feb 16 to Mar 31, 2027 – Release Platform TCK with ratifying impl
  • NoSQL update
    • Update to releases
    • 1.1 adds an optional communications API but is not meant to be like JDBC driver is
    • 1.2 adds query function to the communication API
    • Scott has concerns that there is no commitment from the NoSQL DB vendors to implement the communication API
      • Communication API is meant to be an adapter layer instead of a separate driver from the NoSQL DB’s native driver. Vendors don’t want to have two different drivers.
      • JNoSQL is the main Jakarta NoSQL implementation that will initially provide Communication API implementation, but also get updates from the vendors in that repo. Possibly vendors also implement in their own repositories over time.
      • Vendors may need push from customers to provide implementations.
      • Otavio is meeting with vendors. Believes there are 4 to 5 that are eager to support Jakarta NoSQL.
  • EE 10
  • MicroProfile 7.2
    • New ballots are out. 1st ballots failed due to not being enough people voting for quorum
    • Ballot ends on Friday
  • Jakarta Connectors

Back to the top