Skip to main content

Jakarta EE Platform Call

Date: 2021-02-02


  • Jean-Louis Monteiro (Tomitribe)
  • Werner Keil (Committer)
  • BJ Hargrave (IBM)
  • Kevin Sutter (IBM)
  • Scott Marlow (Red Hat)
  • Otávio Santana (Committer)
  • Dmitry Kornilov (Oracle)
  • Ed Bratt (Oracle)
  • Ivar Grimstad (Eclipse Foundation)
  • Ryan Cuprak (Jakarta EE Ambassadors)
  • Thomas Watson (IBM)
  • Ken Fogel (Jakarta EE Ambassadors)
  • Josh Juneau (Jakarta EE Ambassadors/CJUG)
  • Tanja Obradovic (Eclipse Foundation)
  • Steve Millidge (Payara)
  • Kenji Kazumura (Fujitsu)
  • Scott Stark (Red Hat)

Agenda and Minutes

Schema discussion (continued from the last call)

  • talks about requiring Jakarta EE 8 schemas in EE 9.
  • Action: Add issue for component specs that refer to old schema versions
    • Related to the Broken Link Issue that the Eclipse Foundation team created:

[KWS] Jakarta EE 9.1 Release Plan finalization…

  • Next steps… Get endorsement from Steering Committee and initiate a public ballot for the Specification Committee (and interested parties)
  • Ensure we have a Jakarta EE 9.1 release record in the Eclipse Pages.
  • Fujitsu working on Java SE 11 support for GlassFish

Ken Fogel asked when to expect support fort newer Java versions, e.g. Java 17

  • This would be a requirement for a post-9.1 release (either 9.2 or 10). We need to get past this initial hurdle of supporting Java SE 8 and 11.

[WK] Impact of using selected MP features by Jakarta implementations of NoSQL

  • (where JNoSQL is already impacted) or say Krazo 2.x if it was to use MP REST Client or something else. The usage in specs is currently out of discussions unless the JESP was updated accordingly (jakartaee/JESP/issues/5)
    • Would it be acceptable and also in the interest of “Cloud Native” or “Lean” if an implementation had to carry the overhead of Jakarta EE 9.1, 10 or higher plus at least one earlier version like Jakarta EE 8 because the MP dependencies are not yet there?

Back to the top