Fix a bug where changes to GWC layers won't be propagated to other pods. #570
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.
In vanilla GeoServer,
CatalogConfiguration
is theTileLayerConfiguration
contributed to the app context to serveTileLayer
s (GeoServerTileLayer
) from the GeoServerCatalog
by means of aTileLayerCatalog
.This update contributes a different
TileLayerConfiguration
for the same purpose,GeoServerTileLayerConfiguration
, which is a distributed-event-aware decorator over the actualCloudCatalogConfiguration
implementation ofTileLayerCatalog
.Since
CloudCatalogConfiguration
is therefore not a Spring bean (to avoid registering it as a delegate toTileLayerDispatcher
),TileLayerEvents
need to be relayed fromGeoServerTileLayerConfiguration
toCloudCatalogConfiguration#onTileLayerEventEvict()
.