Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up registration of repositories involving classloading checks on registration [DATACMNS-1619] #2011

spring-projects-issues opened this issue Nov 18, 2019 · 0 comments
in: repository type: enhancement


Copy link

@spring-projects-issues spring-projects-issues commented Nov 18, 2019

Oliver Drotbohm opened DATACMNS-1619 and commented

DATACMNS-1617 unveiled that we apparently inadvertently keep repository interfaces that cannot even be loaded around for inspection (see RepositoryConfigurationExtensionSupport.getRepositoryConfigurations(…) and {….loadRepositoryInterface(…)}}). They effectively cannot be used and will cause errors downstream upon closer inspection, which is probably one reason that the error has not been discovered yet.

Apart from avoiding to keep those around in the initial configuration phase, it creates the impression, we'd adapt to classpath errors in the configuration which we don't do and don't want to

Issue Links:

  • DATACMNS-1617 Automatically drop repository interfaces that cannot be loaded fully
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
in: repository type: enhancement
None yet

No branches or pull requests

2 participants