-
Notifications
You must be signed in to change notification settings - Fork 40.4k
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
Jersey request scoped bean retrieval regression since 2.1.1.RELEASE #15376
Comments
Thanks for the sample. The change in behaviour is due to this commit. You can reinstate the previous behaviour by declaring your own registration of a |
Thanks for your response and pointing me to the right resources! I came up with this:
|
Any chance to get this fixed for 2.1.3? |
We'll see what we can do, but we're not yet sure if it's possible to fix it for everyone without reintroducing a bean overriding problem. As suggested above, you can avoid the problem by registering your own |
Yes, I was just about to try his workaround, but I was hoping for an official fix 🙂 |
While updating a Spring Boot version with Jersey today from
2.0.5.RELEASE
to2.1.1.RELEASE
I stumbled upon a regression regarding request scoped bean retrievel an a Jersey resource. Going back to2.1.0.RELEASE
"fixes" the issue.Reproducer: https://github.com/mweirauch/jersey-scope-issue
The text was updated successfully, but these errors were encountered: