Skip to content
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

Compatibility with RestEasy #5275

Closed
jansupol opened this issue Mar 7, 2023 · 2 comments · Fixed by #5284
Closed

Compatibility with RestEasy #5275

jansupol opened this issue Mar 7, 2023 · 2 comments · Fixed by #5284
Milestone

Comments

@jansupol
Copy link
Contributor

jansupol commented Mar 7, 2023

5232 appears to have broken compatibility with RESTEasy 3.15.6 as demonstrated in the minimal reproducible example (MRE) at: https://github.com/MCMicS/jersey-jackson

Executed actions:

Jersey 2.38: https://github.com/MCMicS/jersey-jackson/actions/runs/4337867360
Jersey 2.39: https://github.com/MCMicS/jersey-jackson/actions/runs/4337871059
Due to this loss of compatibility the Jenkins project was forced to downgrade Jersey back to 2.38 in jenkinsci/jersey2-api-plugin#60 and jenkins-infra/update-center2#688.

@jansupol
Copy link
Contributor Author

jansupol commented Mar 7, 2023

Reported here.

@jansupol
Copy link
Contributor Author

jansupol commented Mar 7, 2023

This is interesting:

  1. Mixing RESTEasy & Jersey
  2. The cause is RestEasy does not support @Inject, only @Context - I would not expect that, I thought RestEasy has a strong integration with Weld -> hence the @Inject support. Jersey switched the constructor from being annotated with @Context to @Inject
  3. @Inject is there to support better the deprecation of @Context in Jakarta REST 4.0
  4. We should think about the compatibility

@jansupol jansupol linked a pull request Mar 21, 2023 that will close this issue
@senivam senivam added this to the 2.40 milestone Mar 22, 2023
@jansupol jansupol modified the milestones: 2.40, 2.39.1 Mar 23, 2023
@senivam senivam added this to the 2.39.1 milestone Mar 23, 2023
This was referenced Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants