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

MergedBeanDefinitions change can be lost if bean is instantiated #28948

Closed
snicoll opened this issue Aug 10, 2022 · 1 comment
Closed

MergedBeanDefinitions change can be lost if bean is instantiated #28948

snicoll opened this issue Aug 10, 2022 · 1 comment
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) theme: aot An issue related to Ahead-of-time processing type: bug A general bug
Milestone

Comments

@snicoll
Copy link
Member

snicoll commented Aug 10, 2022

Freezing the configuration was unfortunately not enough. If a bean is instantiated in an AOT refreshed context, the merged bean definition is flagged stale and it is merged again. As a result, changes made to it are lost, typically the destroy method names.

@snicoll snicoll added type: bug A general bug theme: aot An issue related to Ahead-of-time processing labels Aug 10, 2022
@snicoll snicoll added this to the 6.0.0-M6 milestone Aug 10, 2022
@snicoll
Copy link
Member Author

snicoll commented Aug 10, 2022

markBeanAsCreated is clearing the cache for the bean name.

@jhoeller jhoeller added the in: core Issues in core modules (aop, beans, core, context, expression) label Aug 19, 2022
@jhoeller jhoeller self-assigned this Aug 19, 2022
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) theme: aot An issue related to Ahead-of-time processing type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants