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
Its looks to me like we can have an AutoConfiguration that will work with both Grails or Spring Boot/Micronaut.
If we use AutoConfiguration to setup the DataSource early using the then all the other AutoConfiguration that depend on datasource can be taken advantage of.
as it stands no in grails-plugin, its setup to late in the process for the other Autoconfigurations to get picked up
grails HibernateDatastoreConnectionSourcesRegistrar.postProcessBeanDefinitionRegistry sets up the dataSource but checks for existing first.
in order for other spring boot Autoconfigure (such as actuator metrics) to get picked up then datasource needs to be setup early.
so instead of using HibernateDatastoreSpringInitializer it can autoconfigure the dataSourceConnectionSourceFactory(CachedDataSourceConnectionSourceFactory)
and the Datasource early (which looks like it should be a factory based on dataSourceConnectionSourceFactory)
The text was updated successfully, but these errors were encountered:
Its looks to me like we can have an AutoConfiguration that will work with both Grails or Spring Boot/Micronaut.
so instead of using HibernateDatastoreSpringInitializer it can autoconfigure the dataSourceConnectionSourceFactory(CachedDataSourceConnectionSourceFactory)
and the Datasource early (which looks like it should be a factory based on dataSourceConnectionSourceFactory)
The text was updated successfully, but these errors were encountered: