jakartaee / jakartaee/platform
For future Jakarta EE new versions, I think EJB should not be marginalized.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 230
- Forks
- 77
- Avg merge
- 8d 5h
- Merged PRs (30d)
- 1
Description
For future new versions of Jakarta EE, I don't think EJB should be marginalized. I believe the soul of Jakarta EE lies in EJB. The EJB originally created by Sun is truly charming. EJB is the core, and I think we should enhance and perfect its features — for example, adding stronger AOP capabilities and optimizing the container to make performance take off.
This is just my personal suggestion. I hope my thoughts can be heard. Thank you
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points to inspect. Start by reviewing the Jakarta EE platform scope and existing EJB specifications, then narrow the proposal to a concrete enhancement with acceptance criteria before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100