-
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) #4847
Conversation
Signed-off-by: Jorge Bescos Gascon <[email protected]>
isn't it better to put |
I thought it is too much to move from WARNING to FINE, but I am okay doing that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually 1 change is required:
the main IF here checks if resource is acceptable. Whis includes:
((c.getModifiers() & Modifier.ABSTRACT) != 0
|| c.isPrimitive()
|| c.isAnnotation()
|| c.isInterface()
|| c.isLocalClass()
|| (c.isMemberClass() && (c.getModifiers() & Modifier.STATIC) == 0));
however as per the issue description this warning output is not applicable only to interface.
So, it would be appropriate to write
LOGGER.log( clazz.isInterface() ? Level.FINE : Level.WARNING,
LocalizationMessages.CDI_NON_INSTANTIABLE_COMPONENT(clazz));
Correct, nice catch. |
Signed-off-by: Jorge Bescos Gascon <[email protected]>
Thanks a lot for having this fixed! 👍 🚀 |
#4781