Skip to main content

Jakarta EE Platform Project

Home for the Jakarta EE Platform Team

Jakarta EE Platform Call

Date: 2026-06-02

Present:

  • Jared Anderson (IBM)
  • John Clingan (IBM)
  • Neena Jacob (IBM)
  • Anija K A (IBM)
  • Scott Marlow (IBM)
  • Nathan Rauh (IBM)
  • Brian Stansberry (IBM)
  • Reshmi Vijayan (IBM)
  • Ivar Grimstad (Eclipse Foundation)
  • Michael Redlich (Garden State JUG)
  • Jan Westerkamp (iJUG)

Top of mind for Jared, James

  • No new CCRs left this week. Ivar took care of last week’s CCRs with CoPilot’s help
  • James is still out this week. Due back next week.
  • Ivar is out next week
  • Platform TCK call this Wednesday at 11:00 ET

Jakarta EE 12

  • M5 week 3 of 6 starts this week (M5 ends June 30)
    • A few new component versions working on publishing a new milestone
      • Query 1.0 M2 for instance
      • Persistence 4.0 M4 as well
  • SNAPSHOT builds of the API artifacts are set up
    • Make sure that sources are generated for the individual component specs before updating versions
      • Should be fixed with the 2.0.4 version of the parent pom so that all things are published
      • Had to use an earlier version or earlier milestone for some component specs due to missing source
    • When making update, verify that the job passes
      • Build (build only every hour)
      • Nightly (deploy every “night”)
  • Core Profile progress
    • CDI
      • Beta1
    • JSON-B
      • 3.1.0 M1 is now out
      • Kyle is out for 6 weeks
    • JSON-P
      • No M1 yet, but is planned
    • REST
      • Will start back up when James is back next week
  • Jakarta NoSQL
    • Otavio gives an update about the “driver communication”
    • Discussed a presentation about NoSQL strategy proposal
      • NoSQL being important for AI use cases
    • The spec currently is not dependent on Jakarta Config.
      • Only the implementation (JNoSQL) is currently using Config
      • Vendors are free to configure their implementations as they choose
      • No properties are defined since there is no Config spec in Jakarta yet
    • Currently only one implementation of NoSQL is available
      • Vendors could just provide the API to the user and they provide the implementation (only JNoSQL today) similar to how JDBC is done if an app server vendor doesn’t provide one
      • Debate about if an app server could do this approach and if it makes the specification optional if an implementation doesn’t have to have a NoSQL implementation
      • It would require that NoSQL TCK pass and the vendor would need to specify the NoSQL implementation used
    • Question about how popular NoSQL is
      • Presently users have to use the vendor native NoSQL implementation API
      • Having a standard API could encourage people to use it
    • Part of having this conversation is to start a discussion / vote to include NoSQL in the Jakarta EE 12 Platform
      • The debate about whether the vendor has to provide the API only or has to provide an implementation as well, i.e. if the user brings their own
      • Could require an update to the NoSQL spec and/or in the Platform specification
      • 1.1 not having Config integration isn’t a great thing of course. 1.2 may need to change to 2.0 if adding config makes it a breaking change. User can use vendor specific config or standard config when it is added so it shouldn’t be a breaking change. Could be a breaking change for implementation though, but not necessarily in the specification
      • JNoSQL is using MP Config, so if Jakarta Config has a different namespace, that would break users configuring it possibly
      • But if config is key value pairs and no namespace referenced, there shouldn’t be breaking if namespace is not referenced
      • Also need to decide if it is in the platform only or web / core profile
    • Discussion continue either on a mailing thread or next week’s call
      • Feedback also can be provided to the NoSQL community as well

Config

  • Jan presents the “future directions presentation” on the topic of MicroProfile Config/Jakarta Config
  • Due to NoSQL discussion, this had to be postponed to next week

Back to the top