You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think best practice would be to disable this by default as it hides a lot of duplicate initialization happening behind the scenes with Spring Boot.
For instance, in certain situations I have found when setAllowBeanDefinitionOverriding(true) is on, Spring Boot AutoConfigurations are happening that perform various configurations that are later not even used and completely overridden by Grails. The more dependencies that Spring Boot detects in the class path, the greater this penalty can become.
We should explore disabling this by default as it can always be turned on independently via config if required by the end user:
allow-circular-references is also something that should be considered off by default due to it promotes bad design by resulting in a tightly coupled application.
Feature description
Start Up Time Performance can be severely impacted by the following code:
grails-core/grails-core/src/main/groovy/grails/boot/GrailsApp.groovy
Lines 104 to 107 in 1631e86
I think best practice would be to disable this by default as it hides a lot of duplicate initialization happening behind the scenes with Spring Boot.
For instance, in certain situations I have found when
setAllowBeanDefinitionOverriding(true)
is on, Spring Boot AutoConfigurations are happening that perform various configurations that are later not even used and completely overridden by Grails. The more dependencies that Spring Boot detects in the class path, the greater this penalty can become.We should explore disabling this by default as it can always be turned on independently via config if required by the end user:
spring.main.allow-bean-definition-overriding=true
or
The text was updated successfully, but these errors were encountered: