Skip to content
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

sort BeanDefinitionRegistryPostProcessors added by other BeanDefinitionRegistryPostProcessors [SPR-16043] #20592

Closed
spring-projects-issues opened this issue Oct 4, 2017 · 0 comments
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: backported An issue that has been backported to maintenance branches type: bug A general bug
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Oct 4, 2017

zyro opened SPR-16043 and commented

we are having an ordering problem where one BeanDefinitionRegistryPostProcessor adds multiple other BeanDefinitionRegistryPostProcessor s.
those additional ones get applied in arbitrary order (i.e. not in the order that would correspond to their Ordered precedence).

i dropped a commit comment here: bb971ce#diff-94c72f4a124185c98f882bc9a7038e74R112

ref. also #15258

problem initially found here: apache/grails-core#10824 (comment)

thanks, zyro


Affects: 4.3.11, 5.0 GA

Reference URL: bb971ce#diff-94c72f4a124185c98f882bc9a7038e74R112

Issue Links:

Referenced from: commits 7610210, ad4c8e7

Backported to: 4.3.12

@spring-projects-issues spring-projects-issues added type: bug A general bug status: backported An issue that has been backported to maintenance branches in: core Issues in core modules (aop, beans, core, context, expression) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 5.0.1 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: backported An issue that has been backported to maintenance branches type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants