I migrated a project to 5.3.16 (through Spring Boot 2.6.4) and I had a problem similar to #28002, which so far worked by using a PostProcessor hack. so I tried to reimplement it in the suggested way.
Even though the comments in the ticket state that the preferred form is configurableBeanFactory.registerDependentBean(beanNameDependency, beanNameDepender), I can only make work my postProcessBeanFactory() with configurableBeanFactory.getBeanDefinition(beanNameDepender).setDependsOn(beanNameDependency).
Is this expected? Shouldn't registerDependentBean work the same as setDependsOn? Is it really preferable?
Comment From: snicoll
You didn't really explain how you use the API and why you think the call is being ignored. There are several uses of the register variant in the core container so I don't really know what to do based on the information you've provided.
If you want support, please take the time to share a small sample that we can run ourselves.
Comment From: spring-projects-issues
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Comment From: spring-projects-issues
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.