Andrea Aime (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae9469ffc-5e16-4c2b-b7b0-b9c46e912f9e
) *created* an issue
GeoServer (
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiN2YwZjM3ODE0MDg4NGFjMzkxODQ5M2EyYmMzY2Y5YmEiLCJwIjoiaiJ9
) / Bug (
https://osgeo-org.atlassian.net/browse/GEOS-10046?atlOrigin=eyJpIjoiN2YwZjM3ODE0MDg4NGFjMzkxODQ5M2EyYmMzY2Y5YmEiLCJwIjoiaiJ9
) GEOS-10046 (
https://osgeo-org.atlassian.net/browse/GEOS-10046?atlOrigin=eyJpIjoiN2YwZjM3ODE0MDg4NGFjMzkxODQ5M2EyYmMzY2Y5YmEiLCJwIjoiaiJ9
) GeoServerTileLayer dynamic bounds accidentaly switch to static (
https://osgeo-org.atlassian.net/browse/GEOS-10046?atlOrigin=eyJpIjoiN2YwZjM3ODE0MDg4NGFjMzkxODQ5M2EyYmMzY2Y5YmEiLCJwIjoiaiJ9
)
Issue Type: Bug Assignee: Unassigned Attachments:
image-2021-04-30-11-33-03-908.png, image-2021-04-30-11-33-09-313.png Created:
30/Apr/21 11:33 AM Priority: Medium Reporter: Andrea Aime (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae9469ffc-5e16-4c2b-b7b0-b9c46e912f9e
)
When configuring a new layer in GeoServer, with default tile caching, or when
adding tile caching to a
a layer, the grid subset bonds for it as set to "dynamic", as in, computed on
the fly from the layer
own bounds (which can change over time):
(
https://osgeo-org.atlassian.net/secure/attachment/33693/33693_image-2021-04-30-11-33-03-908.png
) image.png
Seems like a reasonable thing to do. GeoServerTileLayer can compute the bounds
dynamically, while the configuration object backing it,
GeoServerTileLayerInfo, containing the XMLGridSubsets objects, has them with
null bounds.
However, things can become less dynamic.. let's make a GetCapabilities run, the
"dynamic" bounds will be computed so that they can be reported,
and then go back to the layer tile caching tab, you get this:
(
https://osgeo-org.atlassian.net/secure/attachment/33692/33692_image-2021-04-30-11-33-09-313.png
) image.png
If the layer is not saved, and the configuration reloaded, the page goes back
to dynamic bounds. But save the page, even for unrelated changes, and the
bounds are now carved in stone, and I know no way to make them go back to
dynamic.
This seems wrong to me. The issue is happening in this line, updating the xml
gridset bounds while computing the tile layer dynamic bounds:
https://github.com/geoserver/geoserver/blob/main/src/gwc/src/main/java/org/geoserver/gwc/layer/GeoServerTileLayer.java#L999
(
https://osgeo-org.atlassian.net/browse/GEOS-10046#add-comment?atlOrigin=eyJpIjoiN2YwZjM3ODE0MDg4NGFjMzkxODQ5M2EyYmMzY2Y5YmEiLCJwIjoiaiJ9
) Add Comment (
https://osgeo-org.atlassian.net/browse/GEOS-10046#add-comment?atlOrigin=eyJpIjoiN2YwZjM3ODE0MDg4NGFjMzkxODQ5M2EyYmMzY2Y5YmEiLCJwIjoiaiJ9
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100157-
sha1:45b74eb )
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
