eclipse-ee4j / eclipse-ee4j/jersey
Add CDI (not cdi-se) integration module
- Dominant language
- Java
- Stars
- 730
- Forks
- 382
- PR merge metrics
- No merged PRs in 30d
Description
Sometimes people already have a working Tomcat + CDI (doesnt matter if Weld or OWB) setup.
In this case it should be possible to easily add a jersey-cdi module, which relies on the already running CDI container.
A good alternative would be to rename the "cdi-se" module to "cdi" and check there for a running CDI container, first.
Contributor guide
Research direction
Start by locating the existing cdi-se module and understanding how it starts or accesses a CDI container. Compare the proposed jersey-cdi module with the alternative of renaming cdi-se, including support for externally running Weld or OWB in Tomcat. Done means Jersey can integrate with an already running CDI container without requiring a CDI SE setup.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100