When using the pgconfig catalog backend, it replaces the default GWC tile layer catalog with a specialized one to store the tile layers config directly on the database instead of going through the resource store.
To do so, it has to exclude the GWCInitializer bean, as it depends on a TileLayerCatalog.
By doing so, we missed the call to
ConfigurableBlobStore.setChanged(...), resulting in the ConfigurableBlobStore decorator never having its configured flag set to true, and hence never calling the actual BlobStore's put(TileObject) method.
This patch introduces PgsqlGwcInitializer as a replacement for the default GWCInitializer, which takes care of that and also listens to TileEvents to maintain the non-memory-cacheable list of layers in sync at org.geowebcache.storage.blobstore.memory.CacheProvider.
When using the
pgconfigcatalog backend, it replaces the default GWC tile layer catalog with a specialized one to store the tile layers config directly on the database instead of going through the resource store.To do so, it has to exclude the
GWCInitializerbean, as it depends on aTileLayerCatalog.By doing so, we missed the call to
ConfigurableBlobStore.setChanged(...), resulting in theConfigurableBlobStoredecorator never having itsconfiguredflag set to true, and hence never calling the actualBlobStore'sput(TileObject)method.This patch introduces
PgsqlGwcInitializeras a replacement for the defaultGWCInitializer, which takes care of that and also listens toTileEventsto maintain the non-memory-cacheable list of layers in sync atorg.geowebcache.storage.blobstore.memory.CacheProvider.