Skip to main content

Jakarta EE Platform Project

Home for the Jakarta EE Platform Team

Jakarta EE Platform Call

Date: 2023-08-29

Present:

  • Ed Burns (MSFT)
  • Jan Westerkamp (iJUG)
  • Jared Anderson (IBM)
  • Emily Jiang (IBM)
  • Jim Krueger (IBM)
  • Nathan Rauh (IBM)
  • Tom Watson (IBM)
  • Lukas Jungmann (Oracle)
  • Lenny Primak (Individual)
  • Dmitry Kornilov (Oracle)
  • Arjan Tijms (OmniFish)
  • Petr Aubrecht (Payara)
  • Ed Bratt (Oracle)
  • Scott Stark (Red Hat)
  • John Clingan (Red Hat)
  • Cesar Hernandez (Tomitribe)

Agenda and Minutes

Ed Burns taking Discretionary Time Off next week, 2023-09-05.

  • Who can run the meeting? Arjan.

Can someone share their analysis of how the spec committee is responding to our proposed plan? I am a guest on the spec committee, so my analysis is only observational.

Concerns from Red Hat about Jakarta Data itself?

  • https://twitter.com/1ovthafew/status/1696503099601383739
  • Jan TCK dependency to Jakarta NoSQL need to be handled
  • Lenny observes the need to explain to our users the difference between the use cases of Data and Persistence.
    • Where?
      • Tutorial?
      • Blog post?
      • Vendor documentation?
      • YouTube videos?
      • Conference sessions?
    • What
      • Terminology
    • Who
      • Marketing group?
  • Scott Stark stated that Red Hat will increase their level of engagement.
    • To follow
      • GitHub issues for data project
      • Data-dev list
    • Ed to look to Scott Stark to poll for status regarding these

Next steps to get “Make Full / Web profile play nice with MicroProfile maven dependencies” / “Normalize Web Profile Dependencies” PR https://github.com/jakartaee/jakartaee-api/pull/139

  • Jan merged it now
  • Woo!

Maintenance lead role jea-151: define a way forward

  • Ed and Jan to meet 1:1 to define the job to be done.

CDI and CDI EE

  • Breaking up spec/TCK to remove circular dependencies · Issue #687 · jakartaee/cdi (github.com)
  • There will be two ballots for this.
    • Scott will be putting out a new ballot for CDI EE
      • This is either a new spec or a restructuring review.
    • Scott will continue to work with Ivar on this.
  • Make steps to move CDI some integration concerns from CDI itself to the specs that own artefacts? Platform directed (as it’s a cross-spec thing)?
    • Take this as an opportunity to do the right thing for each possible instance of integration challenges. For example Jakarta Servlet and CDI injectability of HttpServletRequest. There is some notion of this being a “built in bean” as defined in CDI.
    • Arjan articulated some history
      • Before: we were not sure if
        • “All the other specs should know about CDI”
        • “CDI should know about all the other specs”
      • Now: we are sure
  • Any steps for a CDI lite API?
    • See above. This is addressed as CDI EE

Maintenance

Back to the top