Skip to content

2.4.0/2.4.1 sprint-boot Rest Repositories initializr project reports lots of Beans is not eligible for getting processed by all BeanPostProcessors [DATAREST-1590] #1921

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

Closed
spring-projects-issues opened this issue Dec 14, 2020 · 2 comments
Assignees
Labels
type: bug A general bug

Comments

@spring-projects-issues
Copy link

Yohann Dumais opened DATAREST-1590 and commented

I just started using Spring Boot and noticed a lot of INFO messages reporting Bean 'X' of type [Y] is not eligible for getting processed by all BeanPostProcessors.

I noticed this behavior when I updated from 2.3.5.RELEASE to 2.4.0.

This repo illustrate the behavior observed : https://github.com/yohanndumais/demo-data-rest

created from spring initializr : https://start.spring.io/... with only Rest Repositories as a dependencies. 

I created this issue against spring-boot 2.4.0 and is still observable with 2.4.1. 

As I am new to Data Rest and spring-boot, I am concerned that I might encounter spring configuration issues. 


Affects: 3.4.2 (2020.0.2)

Reference URL: spring-projects/spring-boot#24322

Backported to: 3.4.3 (2020.0.3)

@spring-projects-issues
Copy link
Author

Oliver Drotbohm commented

Thanks for taking the time to report this! That's fixed and will be part of the next service releases

@odrotbohm
Copy link
Member

I forgot pushing the back-port into the 3.4.x branch. Due to that, the fix has not made it into the recent 3.4.3 release but will instead be shipped with 3.4.4 (due Feb 10th).

odrotbohm added a commit that referenced this issue Jan 14, 2021
…ryRestMvcConfiguration.

Switch to ObjectProvider for all component dependencies in the constructor of RepositoryRestMvcConfiguration. Made the bean definition of AnnotatedEventHandlerInvoker a static bean as it's an application listener and it being an instance method causes extend initialization of the configuration class trickling down into unnecessary bean lookups that early in the lifecycle.

Fixes GH-1921.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants