Jakarta EE Platform Call

Date: 2026-04–07

Present:

• Jared Anderson (IBM)
• Kyle Aure (IBM)
• John Clingan (IBM)
• Neena Jacob (IBM)
• Scott Marlow (IBM)
• Chithra Mini (IBM)
• Anand N K (IBM)
• Nathan Rauh (IBM)
• Reshmi Vijayan (IBM)
• Tom Watson (IBM)
• Michael Redlich (Garden State JUG)
• César Hernández (Tomitribe)
• Bernd Müller (Ostfalia)
• Dmitry Kornilov (Oracle)
• Ivar Grimstad (Eclipse Foundation)

Top of mind for Jared, James

• No new CCRs this week
• 11.0.2 Platform TCK and 3.2.1 Persistence TCK are now published

Jakarta EE 12

• M4 week 2 of 6 starts this week
• Moving Authorization to Web Profile
  • Discuss in order to decide on having a vote
  • Want to do something sooner than later if we want get something done for EE 12
  • Vote or a discussion thread on the mailing list to get the conversation going
  • ACTION start a discussion on the mailing list to see if we can start a vote after next week’s call.
• Jakarta NoSQL 1.1
  • Does this PR address the “driver issue”?
    https://github.com/jakartaee/nosql/pull/218
  • Does the SPI provided in the PR provide for the driver to support over years afterward to support the backend database?
  • Will the vendors use the SPI and provide implementation and maintain them?
  • But does it solve the problem we wanted solved?
  • Does it provide a standard to interact with NoSQL databases?
  • As a user of NoSQL 1.1, can I interact with a supported version of a database until I upgrade to a new version of NoSQL? The vendors currently don’t provide a driver to interact with the DB for NoSQL support.
    • Currently the Jakarta team provides the implementations (Eclipse JNoSQL) to interact with the DBs instead of the vendors providing the implementations.
    • In order to get support / fixes for problems, do users create defects against Jakarta today since vendors aren’t providing implementations?
    • Today the implementation is an adapter layer that interacts with the vendor’s driver
    • NoSQL implementations that are active are Mongo, Cassandra and Oracle NoSQL
    • The current adapter layer approach was to address complaints of vendors
    • Currently it is base contract of behavior, but isn’t like JDBC
    • Will there be a TCK to test the behavior of the SPI and the behavior expected?
      • May not be part of 1.1, but possibly with 1.2
      • SPI in 1.1. Start module in 1.2 and then add new support in 1.3, etc.
      • Would be good to include the roadmap in the project page, possibly https://projects.eclipse.org/projects/ee4j.nosql
  • The PR does not update the specification at all. It just provides an SPI. The specification needs to be updated to specify who is expected to implement the SPI. Vendors implementing the SPI instead of Jakarta.
• EE 11
  • New Platform TCK challenges
    • https://github.com/jakartaee/platform-tck/issues/2678 (Persistence mixed access strategy)
    • https://github.com/jakartaee/platform-tck/issues/2673 (Persistence three
    • https://github.com/jakartaee/platform-tck/issues/2671
• EE 10
  • https://github.com/jakartaee/platform-tck/issues/2544 + https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/1060 is about getting https://ci.eclipse.org/jakartaee-platform/job/JakartaEE-TCK/job/10/job/eftl-jakartaeetck-build-100/ working again.
  • After the project combination, we haven’t done a TCK CI job run with EE 10 in the new location
  • A challenge may be coming soon that would want to include in the service release
  • 10.0.7 has been staged for months, but don’t know the test status of it. May have tested it last summer, but it has been so long.
• Jakarta Futures Direction meetings this month
  • April 16 and 30 are the next meetings
  • April 16 will be about Agentic AI
  • Maybe Jakarta EE 12 update for April 30, TBD
  • Open to additional topics for May and beyond
• Need to update the milestone schedule to adjust for the changes discussed last week in the Top of Mind section
• Previous discussed schedule that needs to be adjusted:
  • M3 Feb 15 to Mar 31
  • M4 Apr 1 to May 15
  • M5 May 16 to Jun 30 – possibly Core profile here
  • M6 Jul 1 to Aug 15
  • M7 Aug 15 to Sep 30 – ideally we release here or soon after
  • M8 Oct 1 to Nov 15
• Want to attract new contributors
  • Update issues with “good first issue” and other things to help new contributors on board