Replies: 2 comments
|
Not that I would be that familiar with this code but it does look like a bug. EDIT: I've drafted a PR -> #56006 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello there
I've hit an issue with using the
@NameBindingannotation to scope a filter to a resource, when that resource uses constructor injection and the binding annotation is applied on the class level. In this combination, Quarkus startup will fail with:Steps to reproduce:
gradlew quarkusDevIf field injection is used instead of constructor injection, or if the binding annotation is applied on the method instead of on the class, Quarkus will successfully start.
I've gone through the docs on
@NameBindingand as far as I understand, one should be able to apply it on the class level. Other relevant information:io.quarkus:quarkus-resteasy)3.35.4and Java25This looks like something that shouldn't happen, but correct me if I'm doing something wrong. If necessary I'll annotate the methods individually, but it would be nice to be able to apply it at the class level.
All reactions