-
Notifications
You must be signed in to change notification settings - Fork 306
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 (Payara Community 5.2021.2)/FISH-6285 #5208
Comments
hi, |
HI @mkarg, Would you be able to verify it on version 5.2021.4 |
@OndroMih Can you please reopen this bug report? I can still reproduce it with Payara 5.2021.8 as there is no Jersey 2.x published yet which actually fixes this problem. The solution is announced for upcoming Jersey 2.36, see here: eclipse-ee4j/jersey#4847. Thanks. |
Hi @mkarg , I reopened this issue but we'll need to wait for the Jersey 2.36 release before we can upgrade Jersey in Payara Server to fix this. Please notify us here when Jersey 2.36 is released in case we miss that. |
Payara Server 5.2022.2 has been upgraded to Jersey 2.36. You shouldn't encounter this issue now in the latest version of Payara Community. Thanks, |
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.Environment
Notes
Originally reported against Payara, but I assume it is a Jersey bug.
The text was updated successfully, but these errors were encountered: