MergedBeanDefinitions change can be lost if bean is instantiated #28948
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
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.
The text was updated successfully, but these errors were encountered: