-
Notifications
You must be signed in to change notification settings - Fork 5
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
Wrong usage of beanDefinition.getBeanClassName() #145
Comments
@itineric thanks for notifying this! I'll create PR for this. |
@itineric I tried to replace the method however I got the null pointer exception. Could you please provide a working PR for this? |
To provide a bit more context, the existing code is using low-level code of the core container that it shouldn't. If you need to get the type of a bean |
Sorry I have been dragged to other tasks for the last months, I'll come back to this issue then. |
@snicoll Thanks for teaching! I'll merge the PR which contains your suggestion of change :D |
Starting from spring 6.0.11, existing code in this library may not work anymore. Some spring
@Bean
annotated with@Provider
and other Jakarta-RS annotations are not recognized anymore (since getBeanClassName() is null) and are not registered in Resteasy as it was with srping version 6.0.10 and previous versions.In the following class: https://github.com/resteasy/resteasy-spring/blob/main/resteasy-spring/src/main/java/org/jboss/resteasy/plugins/spring/SpringBeanProcessor.java , the calls to
BeanDefinition.getBeanClassName()
should beBeanDefinition.getResolvableType().toClass()
See: spring-projects/spring-framework#31242 (comment)
The text was updated successfully, but these errors were encountered: