DWR modernization
Open
Nobody has claimed this yet.
- #34799 by @wezell — closed without merging
stale
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
We need to remove DWR from our stack in an organized way. This insures that any DWR based endpoints are replaced with Jersey endpoints that mirror the functionality. Once we do this and remove all DWR usages , we can be certain that we have the right and working endpoints to rebuild the portlets functionality in NG.
Acceptance Criteria
- Replace DWR calls with REST endpoints
- Have tests for said REST endpoints
- Insure that all functionality is maintained and working
- Remove DWR scripts from the .jsps
Priority
None
Additional Context
No response
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
Start by inventorying DWR calls and scripts in the .jsps, then compare each one with the existing Jersey REST endpoints. Identify the functionality that must be preserved and the tests needed for each REST endpoint. Done means all DWR calls and JSP scripts are removed, equivalent REST endpoints work, and their tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100