Skip to main content

Jakarta EE Platform Project

Home for the Jakarta EE Platform Team

Jakarta EE Platform Call

Date: 2025-02-11
Present

  • James Perkins (Red Hat)
  • Jared Anderson (IBM)
  • Emily Jiang (IBM)
  • Nathan Rauh (IBM)
  • Ed Burns (MSFT)
  • Thomas Watson (IBM)
  • Jan Westerkamp (iJUG)
  • Petr Aubrecht (Payara)
  • Arjan Tijms (OmniFish)
  • César Hernández (Tomitribe)
  • Gurunandan Rao(Oracle)
  • Kenji Kazumura (Fujitsu)

Agenda

Top of mind for Ed, Arjan, Jared

  • Avoid any CN4J discussion.
    • 1. Ed believes this is irreconcilable.
    • 2. Ed believes any discussion about this topic in this forum would be unproductive.
    • 3. We have more important things to discuss.
    • 4. The “two lists” approach is the current plan of record, for config discussions.
  • ACTION: JEA-494-tck-archive-format

TCK Refactoring Jakarta EE 11

Jakarta EE 12

  • Issues labeled for Jakarta EE 12
  • Start talking about dates where component specs get their release plans defined and submitted.
    • Working on making a project board to track Release Plan issues. More to come in the coming week.
  • Extract Jakarta Query from Data and Persistence.
    • Would want to have a creation / release plan created for it if it doesn’t exist already. I know it has been brought up in the past with the specification committee, but not sure where it currently stands.
    • Data spec is on board to use it if it does come to fruition.
    • Proposal link: https://projects.eclipse.org/proposals/jakarta-query?check_logged_in=1. Created by Gavin King.
    • Need to do project inception steps. Create a new project ballot
    • Follow the project creation process:
      • Process is documented here
    • Want to have a committer ballot from at least one person from persistence and data
  • We have discussed a Jakarta HTTP specification in the past
    • Pulls out common HTTP requirements from the servlet / REST specifications into a common specification they both would reference
    • Could pull out a common API for things like header and cookie functions so that there aren’t two different ways of getting headers / cookies for instance.
    • Would need to get a proposal / release plan created for such a specification with a community of people to work on it
    • Arjan would want to be part of the proposed group
    • Would want to have committers from both REST and servlet communities
    • Discussed in the Reza document for EE 12 as well. Reza opened https://github.com/jakartaee/platform/issues/673 for this topic
    • HTTP Request / Response general specifications for both servlet and REST
    • RFC requirements and HTTP 1.x / 2.0 requirements common to both servlet and REST
    • Security authentication mechanisms need to set cookies, headers and request objects and is currently only tied to servlet so cannot be used with REST and MP as easily
    • Jakarta HTTP specification would NOT have a CDI requirement
    • If we added HTTP 3.0 function to EE 12, would it be part of this specification?
    • Should consider adding HTTP 3.0 function to EE 12. ACTION: Jared will open an issue
  • EE12 label is used for platform repository. Want to have component specifications use the same label to find them easily. ACTION: Jared will include in release plan issues and will include in email to component specs.
  • Reach out to prospective specifications to gauge interest?
    • Jakarta Config
      • Use application.properties
        • Name used by other frameworks. Could that cause a conflict?
        • Ordinal choice may be important for existing applications that use this property name since it will end up changing behavior.
        • 100 ordinal suggested to match the MP config properties file ordinal, but that could be confusing on which should win
        • Also discussed just using microprofile-config.properties in Jakarta as well
        • Consider a Jakarta implementation project to work out these issues
        • Smallrye config and Helidon config are MP config implementations
      • Continue to endorse the approach of re-packaging MicroProfile config into a jakarta spec and namespace.
      • MP community talking about removing CDI dependency and changing properties file name as well.
        • MP technical meeting is happening today
        • See proposals being discussed here.
      • Reza is bringing up this topic as well at the Steering committee
    • Jakarta NoSQL
      • A 1.0 release review has been created
      • As per previous conversations, there is concern whether this 1.0 release is sufficient to be included into the platform due to missing things in the initial release? Maybe would need a 1.1 or 2.0 version to be included in the platform?
    • Jakarta MVC
    • Jakarta RPC
  • APIs with SecurityManager / AccessController / PrivilegedAction references
    • APIs with SecurityManager / AccessController / PrivilegedAction references (Platform issue 1018)
      • Activation (issue and PR)
      • Batch (issue and PR)
      • CDI (issue and PR) PR merged already
      • JSON-P (issue and PR)
      • Mail (issue and PR)
      • Persistence (issue and PR)
      • REST (issue and PR) PR merged already
      • Servlet (issue and PR) (just a javadoc update) PR merged
      • Validation (issue and PR) (changes could be done in a service release since 3.1 was new in EE 11)
      • SOAP, XML Binding and XML Web Services also have references to SecurityManager artifacts and could be updated in a minor release independent of EE 12
      • Connector has specification references that need to be cleaned up as well (issue)
        • SecurityPermission annotation that may also need to be deprecated for removal. Needs investigation

Jakarta EE 11

  • What about releasing EE 11 Milestone 5?
    • YESSSSSSS

Back to the top