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
In order to avoid instantiation of any beans involved in the repository configuration (which could trigger unwanted behaviour, like db init script execution) we need to make sure to read the entire configuration from the plain bean definitions.
The text was updated successfully, but these errors were encountered:
Add module identifier and base repository implementation properties.
Fix fragment function previously overriding already set property due to name clash.
Extend tests for bean definition resolution and code block creation.
See: #3279
Original Pull Request: #3282
Associate Repository Bean Definition with RepositoryConfiguration and RepositoryConfigurationExtension attributes to capture configuration details such as the module name or the configuration source.
Introduce RepositoryFragmentsContributor to provide an abstraction for structural fragment implementation allowing to describe the implementation type instead of requiring the implementation object.
Obtain repository fragments from a RepositoryFragmentsContributor (either the configured one or one from a RepositoryFactoryBean).
Closes: #3279
Original Pull Request: #3282
In order to avoid instantiation of any beans involved in the repository configuration (which could trigger unwanted behaviour, like db init script execution) we need to make sure to read the entire configuration from the plain bean definitions.
The text was updated successfully, but these errors were encountered: