Skip to main content

Jakarta EE Platform Call

Date: 2025-01-28
Present

  • Jan Westerkamp (iJUG)
  • Scott Marlow (Red Hat)
  • James Perkins (Red Hat)
  • Jared Anderson (IBM)
  • Anand NK (IBM)
  • Nathan Rauh (IBM)
  • Tom Watson (IBM)
  • Ed Burns (MSFT)
  • John Clingan (Red Hat)
  • Gurunandan Rao(Oracle)
  • Dmitry Kornilov (Oracle)
  • Ed Bratt (Oracle)

Agenda

Top of mind for Ed, Arjan, Jared

TCK Refactoring Jakarta EE 11

  • Will cover high level status today, but more detailed discussion will happen at the TCK call tomorrow
  • Discussed schedule last week at the TCK call
    • Rough estimate that we can say is 1Q, but can’t know that will be attainable due to resources
  • Alwin fixed the outstanding 9 JPA failures for Web Profile.
    • Arjan has not run them yet, but will be doing so once he finishes up some tooling work.
  • TCK call Agenda for tomorrow:
  • Mailing list question about CORBA, javax.CORBA and PortableRemoteObject being checked in signature test or not.
    • These packages are not required by the platform any longer.
  • Release Core, Web, Platform together or independent?
    • Core Profile is available except for the TCK archive discussed in top of mind
    • Web Profile hope to complete 1Q and Platform hopefully by end of 2Q

Jakarta EE 12

  • Issues labeled for Jakarta EE 12
  • Reach out to prospective specifications to gauge interest?
    • Jakarta MVC
      • Included in vendor implementations like glassfish + WildFly. Not sure if used by customers
      • Not sure if they have consumed EE 11 API
      • May not be as popular with customers with new frameworks available
    • Jakarta Config
      • Concerns about integration with Config if added late and not used by component specs. Part of why having this discussion early.
      • Need to determine integration with MP Config
        • CDI integration with Config does bring up some messiness. May need different function for Core Profile vs Web / Platform
        • Does Jakarta Config include all of what MP Config does or a subset of it?
        • Been discussed at the MP technical calls the last few weeks
        • May need to consider a Bridge spec (hosted in Jakarta or MP)
      • Discussed moving MP Config directly to Jakarta Core Profile in the past
        • RedHat opposed doing this move (RedHat does have vote for ballots)
        • Governance and technical issues
      • CN4J would be a place to have these types of discussions about Jakarta and MP Config
    • Jakarta NoSQL
      • Depends on Jakarta Config being included?
      • Would be good to embraced by NoSQL vendors to have multiple implementations
      • Currently have one implementation Eclipse JNoSQL
        • Has proprietary Driver API
        • Implementation has API above what is in the spec that may need to be moved to the spec API for completeness to allow to move to a 1.0 release
        • Includes Jakarta Data integration
      • Supported by Quarkus
      • Open Liberty documents how to use NoSQL with the product
      • Glassfish team would like to include it in the platform per Arjan
      • If included in the platform, could have integration with Data and Security (as a new NoSQL DataStore)
    • Jakarta RPC
  • Plan Reviews
    • Data has a 1.1 release plan and has requested review
    • Any other components working on release plans?
      • Faces team started adding EE12 label to issues
  • 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)
    • 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

Back to the top