Skip to main content

Jakarta EE Platform Call

Date: 2026-02-17

Present:

  • Jared Anderson (IBM)
  • Kyle Aure (IBM)
  • Neena Jacob (IBM)
  • Emily Jiang (IBM)
  • Chithra Mini (IBM)
  • James Perkins (IBM)
  • Nathan Rauh (IBM)
  • Scott Marlow (IBM)
  • Brian Stansberry (IBM)
  • Tom Watson (IBM)
  • Reshmi Vijayan (IBM)
  • John Clingan (IBM)
  • Jan Westerkamp (iJUG)
  • Michael Redlich (Garden State JUG)
  • Arjan Tijms (OmniFish)
  • Ondro Mihalyi (OmniFish)
  • Cesar Hernandez (Tomitribe)
  • Bernd Müller (Ostfalia)

Top of mind for Jared, James

Jakarta EE 12

  • Arjan working on enabling snapshots in some of the projects to enable implementations to make use of the new APIs for experimentation
    • Need milestone builds as well for products to pick up and get repeatable results
    • Staging is also now available for us to be do early staging of milestones as well that can be used for experimentation and validation of the changes
      • Question about expiration of staged resources with the new way of doing things.
      • Need to follow up with Eclipse help desk to get see if the new staging has a retention policy
      • Most components have clean up of their staged resources when they are promoted to be published to maven
  • Eclipse has brought up about some projects being mostly quiet and not needing to run CIs frequently
  • M3 started this week for platform (Feb 15 to March 30)
  • Platform goals this milestone?
    • Component specs move to the new version of the parent POM
    • Get jakartaee API jar populated with component spec milestones
    • Remove SecurityManager usage in APIs 1018
      • Mostly there except for batch as long as specs get releases done
    • Deprecate Application Client 1015
    • Typo fix for Persistence / CDI integration 1150
    • Work with Persistence specification for 1135
    • Research JNDI usage and alternatives for 1105
      • Need to have alternatives for all JNDI usage before could deprecate
      • Quarkus doesn’t make use of JNDI so there may be alternatives or they just don’t support those functions that require JNDI. Possible things that can be discussed
      • ResourceRef for instance for configuring shared vs unsharable connections. What do they use to configure it. Possibly config properties?
      • Do we need Jakarta Config then to help with alternatives for JNDI?
    • Update platform specification to point to new versions that have provided a milestone release
    • https://github.com/jakartaee/platform/issues?q=is%3Aissue%20state%3Aopen%20label%3AEE12
    • CI jobs running Core Profile TCK 11 (12 snapshot maybe even) with Java 21 and Java 25 (may need fixes for running Java 25
      • Discuss more tomorrow at the Platform TCK call
  • Persistence 4.0 TCK commits, not a lot but some changes.
  • Persistence 3.2 TCK release expected soon to address TCK challenges.
  • NoSQL
    • Depends on Config which isn’t available yet for Jakarta EE
    • Still want to hear about whether will have driver support and community implementations
  • Persistence 4.0
    • EclipseLink is low on committers
    • Should vendors consider the alternative of Hibernate for EE 12?
    • Lukas seems to still be active even though not at Oracle any longer
    • If Glassfish wants to stick with EclipseLink, that can be a blocker for GlassFish to be the ratifying implementation for EE 12
    • Need to engage with some of the other vendors that depend on EclipseLink. Chinese vendors have a dependency on EclipseLink as well.
    • Payara helped in the past (EE 9) with GlassFish implementation in the past to get it to be a ratifying implementation
  • Config update

Back to the top