Skip to main content

Jakarta EE Platform Project

Home for the Jakarta EE Platform Team

Jakarta EE Platform Call

Date: 2026-09-01

Present:

  • Jan Westerkamp (iJUG)
  • Jared Anderson (IBM)
  • Kyle Aure (IBM)
  • Neena Jacob (IBM)
  • Anand N K (IBM)
  • James Perkins (IBM)
  • Nathan Rauh (IBM)
  • Reshmi Vijayan (IBM)
  • Tom Watson (IBM)
  • Cesar Hernandez (Tomitribe)
  • Michael Redlich (Garden State JUG)

Top of mind for Jared, James

  • CCRs
    • One new CCR came in yesterday #1351
      • This CCR is from Vidocq that we discussed a few weeks ago
      • It is Java 25 CCR with a failure due to challenge #2730 not being addressed yet to create a new service release
      • Follow up with Tanja and the spec committee tomorrow since they are not a member yet? Probably should have some text explaining that.
    • There is a broken certification link on an old CCR, see https://github.com/jakartaee/platform/issues/1092#issuecomment-5477915738.
      • May want to follow up at the spec committee as well with Payara rep.
  • JakartaOne Livestream CFP still open. Please submit your talk! https://sessionize.com/jakartaone-livestream-2026
    • Deadline updated to Sept 22

Jakarta EE 12

  • M7 week 3 of 6 starts this week (M7 ends September 30)

  • Core Profile progress
    • Targeting 4Q 2026. JakartaOne is December 1

    • Core profile spec updates should be started as well to reflect version changes at least.

    • CDI
    • JSON-B
      • 3.1.0 M1 API and TCK is out
      • M2 is in good shape. Just a few updates to be made for some testing and spec for record support
      • 3.1.0 M1 Yasson is released. It passes the M1 TCK
    • JSON-P
      • No M1 yet, but is planned
    • REST
      • No M1 yet
      • Waiting for reviews before anything can be merged
      • Committers have been encouraged to review the relevant PRs
  • Web Profile progress
    • Authorization
      • No API update yet in Jakarta
      • Need Platform vote to move it to Web Profile
        • Look to start that vote this milestone
    • Servlet
      • 6.2.0 M2 API was released around May
        • The specification page still needs to be updated to reflect this version
    • Pages
      • 4.1.0 M2 API also release around May
    • Tags
      • 3.1.0 M2 API released in July
    • Faces
      • 5.0.0 M6 API released last week
      • Glassfish vNext has faces updates in it
    • Security
      • 5.0.0 M2 API released in May
      • Still need to rehome the API without “enterprise” in the group name
      • Glassfish vNext has security updates in it
    • Transaction
      • Spec / API updates, but no milestone of the API yet.
      • TCK move over from platform PR is there for them to accept
        • Depends on some TCK shared libraries that would want to have an EE 12 TCK milestone release
    • Concurrency
      • 3.2.0 M2 API released in March
      • Working on API updates for issues found
      • IBM Liberty is working on implementation. It is the usual ratifying implementation
    • Data
      • 1.1.0 M3 API released in April
      • In progress on a M4. Draft PR being worked on.
        • Waiting for the 1.0 service release to be merged first. Then will take it out of draft
      • Depends on Query releasing before can do final release
    • Expression Language
      • 6.1.0 M2 API released in May
    • Persistence
      • 4.0.0 M6 API released in July
        • The specification page still needs to be updated to reflect this version
      • Depends on Query releasing before can do final release
    • Query
      • 1.0.0 M2 of the specification is available
      • No API
      • TCK covered by Data, NoSQL and Persistence
    • Validation
      • 4.0.0 M1 API released in October 2025
    • WebSocket
      • 2.3.0 M2 API released in January
    • Enterprise Beans Lite
      • 4.1 has no traction
  • Open Forum
    • Future Directions meeting
      • Still working on plan for September
    • MicroProfile
      • Starts back up this month. Community call today.

The previous Agenda and minutes are below.

Jakarta EE Platform Call

Date: 2026-08-25

Present:

  • Jared Anderson (IBM)
  • Kyle Aure (IBM)
  • Scott Marlow (IBM)
  • James Perkins (IBM)
  • Nathan Rauh (IBM)
  • Ivar Grimstad (Eclipse Foundation)
  • Jan Westerkamp (iJUG)
  • Michael Redlich (Garden State JUG)

Top of mind for Jared, James

  • No new CCRs

  • If you are working on a component spec update, make sure your specification includes the 1.1 or 2.0 of EFSL (Eclipse Foundation Specification License), not 1.0.
    • If currently you have 1.0 move to 2.0
    • If currently you have 1.1, you can stay at 1.1 or move to 2.0
    • Don’t confuse this with EPL (Eclipse Public License) 2.0 for the API and implementation license
  • https://github.com/jakartaee/validation/issues/345 was brought up recently in slack
    • Trying to find a home in the Jakarta ecosystem for this idea. Validation may not be the right location. Soliciting any ideas.
    • REST has a default value concept for its *Param annotations
    • Could maybe standardize something in Jakarta Annotations and be used in multiple specifications (i.e. CDI, Data, Persistence, etc)?
    • Jakarta Config also has a default mechanism.
    • Annotations might be the right place to home the annotations, but other specs would need to define their use.
  • New platform TCK issue: #2734
    • Intermittent failure
    • Seems to be a fair challenge and can be fixed with a simple update to the test
    • Sept 2 is the next Platform TCK call
    • Scott also sent an email over to EJB since the EJB TCK is there for future use

Jakarta EE 12

  • M7 week 2 of 6 starts this week (M7 ends September 30)

  • Core Profile progress

    • Targeting 4Q 2026. JakartaOne is December 1

    • CDI
    • JSON-B
      • 3.1.0 M1 API and TCK is out
      • M2 is in good shape. Just a few updates to be made for some testing and spec for record support
      • 3.1.0 M1 Yasson is released. It passes the M1 TCK
    • JSON-P
      • No M1 yet, but is planned
    • REST
      • No M1 yet
      • Waiting for reviews before anything can be merged
      • Committers have been encouraged to review the relevant PRs
  • Web Profile progress
    • Servlet
      • 6.2.0 M2 API was released around May
    • Pages
      • 4.1.0 M2 API also release around May
    • Tags
      • 3.1.0 M2 API released in July
    • Faces
      • 5.0.0 M6 API released last week
      • Glassfish vNext has faces updates in it
    • Security
      • 5.0.0 M2 API released in May
      • Still need to rehome the API without “enterprise” in the group name
      • Glassfish vNext has security updates in it
    • Transaction
      • Spec / API updates, but no milestone of the API yet.
      • TCK move over from platform PR is there for them to accept
        • Depends on some TCK shared libraries that would want to have an EE 12 TCK milestone release
    • Concurrency
      • 3.2.0 M2 API released in March
      • Working on API updates for issues found
      • IBM Liberty is working on implementation. It is the usual ratifying implementation
    • Data
      • 1.1.0 M3 API released in April
      • Working on a M4. May be coming later this week or next.
      • Depends on Query releasing before can do final release
    • Expression Language
      • 6.1.0 M2 API released in May
    • Persistence
      • 4.0.0 M6 API released in July
      • Depends on Query releasing before can do final release
    • Query
      • 1.0.0 M2 of the specification is available
      • No API
      • TCK covered by Data, NoSQL and Persistence
    • Validation
      • 4.0.0 M1 API released in October 2025
    • WebSocket
      • 2.3.0 M2 API released in January
    • Enterprise Beans Lite
      • 4.1 has no traction
    • Authorization
      • No API update yet in Jakarta
      • Need Platform vote to move it to Web Profile
        • Look to start that vote this milestone
  • Open forum
    • Vaibhav Vishal committer election open for EclipseLink
    • No news on the next Futures call. Hope to have one in September
    • Jakarta RPC is being terminated in the coming weeks

Back to the top