Skip to content

GeoServer Cloud 2.28.5.1

Choose a tag to compare

@groldan groldan released this 09 Sep 02:45
· 325 commits to main since this release
v2.28.5.1
50aabef

GeoServer Cloud 2.28.5.1

Patch release on top of 2.28.5.0. If you are running 2.28.5.0, upgrade. The REST resource API is broken in that version.

Fixed

REST resource API failing with 500s and 404s (#935 )

The GWC filter now only claims genuine GWC dispatch paths: /gwc as a whole segment, alone or behind a /{workspace} or /{workspace}/{layer} virtual service prefix, never under another dispatcher's base path. The same fix also makes /rest/resource/** honor the format query parameter for content negotiation, so ?operation=metadata&format=json on a .txt resource, and directory listings with an Accept header preferring such a type, no longer fail.

REST config writes corrupting OGC API and INSPIRE settings (#966 — fixes #872)

The restconfig service was missing the XStreamPersister initializers that handle complex metadata map values.
Consequences: a GET + PUT round trip on /rest/services/wfs/settings replaced the OGC API Features conformance object with a string and broke WFS with a ClassCastException; cascaded stored query configurations and OGC API links were corrupted the same way; the INSPIRE initializer was never registered at all. Initializers are now contributed by their owning modules through class-conditional auto-configuration, so every service gets them. Also restores the missing propertySelection field in the Jackson conformances module, which the pgconfig backend was silently dropping.

Importer extension failing on startup with NoClassDefFoundError (#937 — addresses #912) — thanks @articque

The Importer bean shared by webui and restconfig calls LoggingUtils.checkBuiltInLoggingConfiguration(), whose bytecode references org.apache.logging.log4j.core.config.Configuration. RELINQUISH_LOG4J_CONTROL makes the call a no-op at runtime, but the JVM still resolves the type during class verification, so enabling the Importer extension failed immediately. log4j-core is now a direct dependency of the importer extension module, so every app enabling it gets it transitively rather than each app declaring it.

Dependencies

  • Upgraded to the latest GeoServer 2.28.x (#942, #961)
  • AWS SDK modules are now managed from the 1.12.797 BOM, dropping software.amazon.ion:ion-java 1.0.2, which is no longer receiving releases and was still pulled in by the 1.12.261 pin in gwc-aws-s3 (#973)

Build

No runtime impact; listed for completeness.

  • GeoServer is built from a shallow submodule instead of consumed from GitHub Packages (#928)
  • Simplified GeoServer submodule updates (#941)

Full Changelog: v2.28.5.0...v2.28.5.1