Deliver Jakarta Enterprise Beans Specification Version update for Jakarta EE 9

[kwsutter]

Is your feature request related to a problem? Please describe.
Jakarta EE 9 is the next major release, with the main focus of moving from the javax namespace to the jakarta namespace.

Describe the solution you'd like
This issue will be used to track the progress of this work effort via the Jakarta EE 9 Project board.

Additional context
Jakarta EE Specification Process
Eclipse Project Handbook
Eclipse Release Record for Jakarta EE 9

ToDo

• Create Eclipse Release Record in your respective Jakarta Specification Project.
  Most Component Release Records will just reference the Jakarta EE 9 Platform Release Plan. But, if your Component deviates at all from the Platform Release Plan, then a description of the changes will be required in the Release Record.
  Skeletal EJB 4.0 Release Record was created, but more detailed information is required before we can initiate a ballot...
• Initiate a ballot for your Jakarta Release Record/Plan.
  Again, if your component is only doing the required minimum as defined by the Jakarta EE 9 Platform Release Plan, then no separate ballot is required. You are already approved. But, if your component deviates from the Platform Release Plan, then you will need to initiate your own ballot as defined by the Jakarta EE Specification Process.
• Jakarta-ize your Specification document (if applicable)
  Many of the Jakarta EE components now have the source for their Specification documents. It is strongly recommended that these Specification documents are properly updated to represent Jakarta EE instead of Java EE. Some helpful instructions are documented here.
• javax -> jakarta Spec updates
  If your component has Specification source, then all javax package references need to be updated to use jakarta package references.
• javax -> jakarta API updates
  Your component APIs need to move from using the javax namespace to using the jakarta namespace.
• Release Candidate (RC) of Jakarta API in Maven Central
  A Release Candidate of your component API should be pushed to Maven Central as soon as humanly possible. This will allow other dependent components to utilize your APIs as they are updating their APIs. Multiple revisions of these Release Candidate APIs are allowed (and probably expected) during the development cycle.
• javax -> jakarta TCK updates
  Your component TCK needs to be updated to use the jakarta namespace.
• javax -> jakarta Compatible Implementation updates
  Your compatible implementation that will be used to demonstrate completeness of the Specification needs to be updated to use the jakarta namespace.
• Final Jakarta API available in Staging Repo
  When ready, your final version of the API needs to be staged to get ready for the PR review and approvals.
• Draft Specification and Apidoc PRs ready for review
  Like we did for Jakarta EE 8, draft PRs need to be created and reviewed in preparation for the final ballots.
• Release Review Ballot started
  Each Jakarta EE component will need to initiate a separate Release Review ballot after proper reviewing has completed. To be clear, there will not be a blanket Release Review for all of Jakarta EE 9 like we did for the Plan Review. Each component needs a separate Release Review.

[kwsutter]

Can I ask this team to please create and assign the following labels to this Issue? Thank you!
[Epic]
[wave:5]

[kwsutter]

Any activity on this Issue? According to our Jakarta EE 9 Release Plan and noted in our project board, any potential individual Release Plans are required by Feb 1. Please communicate any hurdles to meeting this goal. Thanks!

[hussainnm]

javax -> jakarta TCK updates is done in jakartaee/platform-tck/pull/170

[ederks85]

Opened #99 for processing "Jakarta-ize your Specification document (if applicable)"

[hussainnm]

javax -> jakarta Compatible Implementation updates
eclipse-ee4j/glassfish@ed5e731

Currently Glassfish eclipse-ee4j/glassfish#22983 is waiting on RC2 of ejb-api.

[kwsutter]

According to status from @ederks85 on the Community mailing list, the EJB Spec has been Jakarta-ized for Jakarta EE 9. I'm marking those items complete.

[jeanouii]

Not sure where we are at with this task.
Did a quick check on the javax namespace in TCK and looks good to me
Here is the list of remaining mentions

egrep -h -o "javax.[^ ;<]+" -R src/com/sun/ts/tests/ejb* | sort | uniq
javax.naming.*
javax.naming."
javax.naming.Binding
javax.naming.Context
javax.naming.Context)
javax.naming.InitialContext
javax.naming.InitialContext()
javax.naming.NameClassPair
javax.naming.NameNotFoundException
javax.naming.NamingEnumeration
javax.naming.NamingException
javax.rmi.
javax.rmi.PortableRemoteObject
javax.sql.*
javax.sql.DataSource
javax.sql.Datasource.
javax.transaction.xa.XAResource
javax.transacton.TransactionRequiredException

If I'm not mistaken, only the last one is not valid, right?
XAResource is part of the JDK
TransactionRequiredException should be JTA so in the jakarta package.

[hussainnm]

We still have around 100 test failures in TCK
https://ci.eclipse.org/jakartaee-tck/job/eftl-jakartaeetck-run-900/5/junit-reports-with-handlebars/testSuitesOverview.html

[jeanouii]

Yes it's been actively worked but I was more looking at the javax -> jakarta item in the list.

[smillidge]

Yes last one is in an incorrect package