Skip to main content

Jakarta EE Platform Call

Date: 2024-06-18

Present:

  • Jared Anderson (IBM)
  • Emily Jiang (IBM)
  • Jim Krueger (IBM)
  • Riva Philip (IBM)
  • Nathan Rauh (IBM)
  • Tom Watson (IBM)
  • Ed Burns (MSFT) (second half)
  • Arjan Tijms (OmniFish
  • James Perkins (Red Hat)
  • John Clingan (Red Hat)
  • Lukas Jungmann (Oracle)
  • Scott Stark (Red Hat)
  • Jan Westerkamp (iJUG)
  • Scott Marlow (Red Hat)
  • Dmitry Kornilov (Oracle)
  • Ed Bratt (Oracle)
  • Petr Aubrecht (Payara)
  • César Hernández (Tomitribe)

Agenda and Minutes

Top-of-mind from Ed and Arjan

  • Logistics
    • Emily will run the first 30 minutes of today’s meeting due to a schedule conflict on Ed’s calendar.
  • M3 release?
    • M3 has been released. Small mistake found in Jakarta Faces. Jakarta APIs referred to Jakarta Faces m2. UPDATE: Faces Final release was slated for M4 so it is correct that M3 includes a Milestone release of Faces.
    • M4 will refer to the final Jakarta Face release 4.1.
    • EE 11 page needs to point to M3.
  • Security ballot: Jean-Louis spec mentor role action?
    • Ballot in progress.
    • Security ballot will end on 26th June.
  • Marlow: https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl//jakarta-jakartaeetck-10.0.5.zip
    • https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/10.0.x/123/ has list of git changes
    • Tags test update for Java 21, JDBC test update for Java 21
    • Staged. Changes look good. Please test it out and provide feedback.
    • Would like to pull in additional tck challenges. Will add test excludes for Jakarta Persistence challenges. Another challenge is for schemas of any pre-jakartaee 8 schema.
    • Labor intensive to publish tcks. Safe to include more changes.
    • Are there other component spec tck changes?
      • Concurrency changes accepted
      • Security changes accepted - more changes to happen
      • If you experience other Java 21 failures, please shout.
  • Marlow: Note as per https://jakarta.ee/specifications/platform/11/, all optional Specifications are removed.
    • EE 11 Platform Specification has not yet been updated for this change.
      • This issue has been created to track the changes from the specification doc.
      • Related Platform TCK issue is https://github.com/jakartaee/platform-tck/issues/1296
        • TCK tests will be removed for the optional specs that are compatible with EE 11, but no longer required
          • Removing optional TCK tests should be done by moving such tests to an inactive folder in tckrefactor branch. Or consider tagging the tests.
        • Post Platform 11 TCK release, the optional spec TCKs will be done due to lack of time to get the 11 release out. Vendors can use EE 10 for the optional spec TCKs

TCK Refactoring Progress Report

Explanation

Specification = Name and version of spec in EE 11

Standalone (TCK) = The TCK is hosted and taken care of by the spec itself (is an independent TCK, and run independently)

Platform (TCK) = The TCK is hosted inside the platform TCK (at https://github.com/jakartaee/platform-tck) and run as part of that platform TCK

Refactored = [the refactoring meant by Scott Marlow that’s holding up the release]

Standalone (Mode) = The TCK, either as standalone TCK or as Platform TCK, passed in Standalone mode

Platform (Mode) = The TCK, either as standalone TCK or as Platform TCK, passed in Platform mode

</table> * In previous releases we used a wiki page that was cleared, so it is a blank slate currently for EE 11. * [EE 11 Platform TCK estimation worksheet](https://docs.google.com/spreadsheets/d/1YVSMWBYnzQg7gHIMZA1cZT9HmQIyME1XeW7Y8LOxulc/edit#gid=0) * [https://www.eclipse.org/lists/jakartaee-tck-dev/msg02022.html](https://www.eclipse.org/lists/jakartaee-tck-dev/msg02022.html) is email from Scott Stark about the “Initial appclient protocol” which looks good to me. * [https://github.com/scottmarlow/jakartaee-tck-tools/tree/rewritejpa](https://github.com/scottmarlow/jakartaee-tck-tools/tree/rewritejpa) has more changes for refactoring the Persistence tests. * We are now getting zero compile failures (or at least I am). * Next step will be syncing with the “Initial appclient protocol” changes. * We do need appclient container vehicle testing for Persistence.

Passed
Specification Standalone

(TCK) </td>

Platform

(TCK) </td>

Refactored Standalone

(Mode) </td>

Platform

(Mode) </td> </tr>

Jakarta EE Platform 11* n/a n/a
Jakarta EE Web Profile 11 * n/a n/a
Jakarta EE Core Profile 11* n/a n/a
Jakarta CDI 4.1* ✔️
Jakarta Data 1.0* ✔️
Jakarta Activation 2.1.2*
Jakarta Annotations 3.0*
Jakarta Authentication 3.1* ✔️ ✔️
Jakarta Authorization 3.0* ✔️ ✔️
Jakarta Batch 2.1
Jakarta Concurrency 3.1* ✔️
Jakarta Connectors 2.1
Jakarta Debugging Support for Other Languages 2.0
Jakarta Dependency Injection 2.0.1
Jakarta Enterprise Beans 4.0.1
Jakarta Expression Language 6.0 ✔️ ✔️ n/a
Jakarta Faces 4.1* ✔️ n/a ✔️
Jakarta Interceptors 2.2* Part of CDI
Jakarta JSON Binding 3.0 ✔️
Jakarta JSON Processing 2.1.2* service release ✔️
Jakarta Lang Model 4.0.1 ✔️
Jakarta Mail 2.1.2* service release
Jakarta Messaging 3.1
Jakarta Persistence 3.2* ✔️ ✔️
Jakarta RESTful Web Services 4.0* ✔️ ✔️
Jakarta SOAP with Attachments 3.0
Jakarta Security 4.0* ✔️ n/a ✔️
Jakarta Server Pages 4.0* ✔️ n/a ✔️
Jakarta Servlet 6.1* ✔️ n/a ✔️
Jakarta Standard Tag Library 3.0.1*
Jakarta Transactions 2.0.1
Jakarta Validation 3.1*
Jakarta WebSocket 2.2*
Jakarta XML Binding 4.0

Back to the top