Enterprise beans 4.1 (under development)

[tadamski]

Include the following in the PR:

• A directory in the form enterprise-beans/4.1 .
• An index page enterprise-beans/4.1/_index.md following template
• [x ] Title should be on the form "Enterprise beans 4.1 (under development)"
• Includes a plan for the release. Usually, a couple of statements is enough. Otherwise, a link to a document describing the release.
• Includes a detailed description of any backward incompatibility N/A
• Declares optional features if there are any N/A
• Includes minimum Java SE version
• Describe any updates or required changes including splitting out the TCK
• Link to updated release record

[netlify]

✅ Deploy Preview for jakartaee-specifications ready!

Name	Link
🔨 Latest commit	c775580
🔍 Latest deploy log	https://app.netlify.com/sites/jakartaee-specifications/deploys/67ffb7a844920a000873649b
😎 Deploy Preview	https://deploy-preview-826--jakartaee-specifications.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jhanders34]

@tadamski thank you for creating this draft release plan. Can you update the description to use the template: https://github.com/jakartaee/specifications/blob/master/plan_review_pr_template.md and update things accordingly for the checklist? You do not appear to be a committer for Enterprise Beans, so you cannot create a new release on the project page: https://projects.eclipse.org/projects/ee4j.ejb. You will need to work with a committer in order to get that updated.

[tadamski]

@jhanders34 I have changed the title and mentioned lack of backwards incompatible changes. Are there any more changes necessary?

[chengfang]

LGTM

[jhanders34]

@jhanders34 I have changed the title and mentioned lack of backwards incompatible changes. Are there any more changes necessary?

The description (first comment) still needs to have the checklist that is in the template that I referenced. Copy the raw version of the link in my previous comment and edit the first comment to have that checklist and then checkoff the things on the list that you believe are complete.

One of those checklist items will have you uncomment

* [Jakarta Enterprise Beans 4.1 Release Record](https://projects.eclipse.org/projects/ee4j.ejb/releases/4.0/plan)

and it should point to 4.1 in the link instead of 4.0.

Also you will want to have the line about ratifying implementation and not just Compatible implementation.

[dblevins]

Note to the specification committee, the contents of this PR are still under discussion in the EJB spec group. No plan has yet to be agreed.

[tadamski]

@jhanders34 I have updated the description and added release record link (but for now it is invalid because I don't have the rights to create release plan).

[AngeloRubens]

Hi All,

why not think about standardizing this implementation present in wildfly? like this:

Ejb Over http/Http2

https://github.com/wildfly/wildfly-http-client/blob/c8f7f52a084714b6c5a5f993ebf2f89ac1f52751/docs/src/main/asciidoc/wire-spec-v3.asciidoc

Distributed EJB Transaction over http/http2

https://developers.redhat.com/articles/2024/08/29/distributed-transactions-jakarta-ee-10-and-wildfly#

[jhanders34]

@tadamski with Tracy creating the Release Record, are you ready for the release plan to move to the mentor for review and ballot?

[dblevins]

@jhanders34 We've discussed and removed the EJB over HTTP feature. This is now ready to go up for vote.

[tadamski]

@jhanders34 yes I'm ok with release plan to move to review and ballot