Minimal reproducible example
When registering new bean definition in place of existing one, CUBA platform don't fully restore dependencies.
Suspected code
It seems that a call to super.resetBeanDefinition(beanName); on line 77 modifies dependencies not only for current bean, but for dependant beans also. On a next recursive call, getDependentBeans(beanName) returns modified dependant beans list, so in some cases dependencies are not fully restored.
Environment
Description of the bug or enhancement
Minimal reproducible example When registering new bean definition in place of existing one, CUBA platform don't fully restore dependencies. Suspected code It seems that a call to
super.resetBeanDefinition(beanName);on line 77 modifies dependencies not only for current bean, but for dependant beans also. On a next recursive call,getDependentBeans(beanName)returns modified dependant beans list, so in some cases dependencies are not fully restored.Expected behavior all bean dependencies restored
Actual behavior not all dependencies restored