Startup DiskQuotaMonitor on context init, rather than after bean properties are set #1147
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…er bean properties are set This makes spring initialization much easier and avoids risk of xml configuration not yet being available
jodygarnett
force-pushed
the
diskquota_lazy_startup
branch
from
7df42f7
to
2b5a3ba
Compare
|
The downstream geoserver build is failing on gs-metadata (a common problem) so I believe this PR is ready for review. |
|
Integration build restarted, downstream should be sane now, let's see. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes spring initialization much easier and avoids risk of xml configuration not yet being available.
See https://osgeo-org.atlassian.net/browse/GEOS-11032 for background information.