Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] Jakarta EE Spec Committee Approved Meeting Minutes - January 26th, 2022

Jakarta EE Spec Committee - January 26th, 2022

Attendees (present in bold):

Kenji Kazumura - Fujitsu

Tom Watson - IBM - Emily Jiang

Ed Bratt - Oracle - Dmitry Kornilov

Andrew Pielage - Payara

David Blevins - Tomitribe - Jean-Louis Monteiro, Cesar Hernandez

Ivar Grimstad - PMC Representative

Marcelo Ancelmo - Participant Member - Martijn Verburg

Werner Keil - Committer Member

Jun Qian - Primeton - Enterprise Member

Zhai Luchao -  Shandong Cvicse Middleware Co. - Enterprise Member


Eclipse Foundation: Tanja Obradovic, Paul Buck (chair)

Guests: Scott Stark, Scott Marlow

Past business / action items:

  • Approval is requested for the meeting minutes from the January 12th, 2022 meeting as drafted - Approved subject to the comments below:

    • Ed raised a concern regarding the minutes as written, they said there was a proposal for a ballot, it was unclear that the spec committee would proceed to ballot?

    • Our process as a spec committee for electronic ballots needs to be stated and agreed to. Action: The chair to propose a process for electronic ballots in the next meeting.


  • Jakarta EE package namespace for TCK’s:

    • Ballot 

      • Resolution: “vote to approve the Jakarta TCK package name ee.jakarta.tck.[spec]

  • Result:

  • Observation - Questions and discussions have taken place on the mailing list regarding: 

    • 1.There was  confusion around what was decided regarding TCK package names and how it is to be applied to spec projects in Jakarta EE 10, and subsequent releases was not provided

      • Action: Package namespace decision is for future releases [Emily]

    • 2. Usage of the jakarta package namespace for tests within a TCK

      • Action: Update the TCK Operations document [David]

    • 3. General guidance on the authorized usage of the jakarta package namespace governed by the Eclipse Foundation and the Working Group

      • Action: Write down somewhere that the jakarta namespace is for APIs of Jakarta specifications. Update the JESP and add boilerplate to all the specification documents [Ivar to draft]

David provided a summary and a proposed revised resolution:

  • Discussion on next steps to resolve the situation we are in the midst of regarding the TCK package namespace

Restful Web Services is stuck, it has tests in the jakarta namespace, what should they do (item 2.)?

  • They must change to something else [Ivar to suggest text, send to Spec Committee for review and then comment on the PR]

Some (most) app servers have filters for javax and jakarta, that could prevent certain tests from running if they are in the jakarta namespace

  • Is the TCK part of the spec and therefore can include code in the jakarta namespace? 

    • This is not desirable and needs to prohibited, TCKs are meant to be application code, they are not part of the spec

    • TCK needs to avoid usage of the proprietary namespace

    • Update the TCK Operations document with the namespace restriction

Proposal: work on 2. Immediately, get to 1. and 3. over time.

The following item were not covered and will be added to the agenda for next meeting

Please respond to the Jakarta EE Working Group Member Survey google form

Back to the top