-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug Report: CDI tries to instantiate interface (Jersey 2.30) #4781
Milestone
Comments
This was referenced Jun 14, 2022
Closed
1 task
This was referenced Jun 18, 2022
This was referenced Dec 7, 2022
Closed
1 task
This was referenced Jan 6, 2023
Merged
This was referenced Feb 11, 2023
Closed
1 task
This was referenced May 11, 2023
This was referenced Jun 1, 2023
This was referenced Jun 4, 2023
This was referenced Jun 15, 2023
This was referenced Jul 6, 2023
This was referenced Aug 28, 2023
This was referenced Jan 16, 2024
1 task
This was referenced Apr 13, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
An interface annotated by
@Path
found in a WAR file results in a warning that CDI cannot instantiate it.Expected Outcome
No instance is created, and no warning is found in the log file.
Current Outcome
No instance is created, but a warning is found in the log file:
Steps to reproduce
Deploy a WAR file containing an interface annotated by
@Path("")
, then send a request against the base URL of the WAR file.Workaround
Remove
@Path
from the interface implemented by the resource class, but solely use@Path
directly at the resource class itself.Notes
Originally reported against Payara, but I assume it is a Jersey bug.
The text was updated successfully, but these errors were encountered: