jakartaee / jakartaee/platform
Deprecate Application Client Container (ACC)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 230
- Forks
- 77
- Avg merge
- 8d 5h
- Merged PRs (30d)
- 1
Description
The ACC was never really that popular and it's primary target use cases - remote EJB and Applets - are long out of favor. It should be deprecated to keep the platform lightweight, agile, and forward looking.
There are already many better alternatives for many years now. Just some of them:
* Not using Java SE clients in the first place and use JavaScript clients instead.
* Using REST, WebSocket, etc instead.
* Using vendor specific remote JNDI client libraries.
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. Start by reviewing how the Jakarta EE platform specification references the Application Client Container and its remote EJB and Applet use cases. Done requires a defined deprecation scope and corresponding platform-specification changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100