HTM-1852 | HTM-1964: Upgrade to GeoTools 35.0 and re-instate GeoJSON extract

[mprins]

• Initialise GeoTools on application startup and set our preferred entity resolver
• Add an entity resolver that explicity allows DescribeFeatureType (dynamic schema) requests to work around https://osgeo-org.atlassian.net/browse/GEOT-7916

[github-actions]

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ⚠️ 2 package(s) with unknown licenses.

See the Details below.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA 76c9d0f.

Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

License Issues

pom.xml

Package	Version	License	Issue Type
org.geotools:gt-bom	35.0	Null	Unknown License
org.geotools:gt-excel-writer	35.0	Null	Unknown License

Allowed Licenses:

MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0, LGPL-2.1-only, EPL-2.0, EPL-1.0, LicenseRef-scancode-oracle-free-2018

Excluded from license check:

pkg:maven/org.eclipse.angus/jakarta.mail@2.0.5?type=jar, pkg:maven/jakarta.ws.rs:jakarta.ws.rs-api@4.0.0?type=jar, pkg:maven/jakarta.xml.bind:jakarta.xml.bind-api@4.0.5?type=jar

OpenSSF Scorecard

Package	Version	Score	Details
maven/org.geotools:gt-bom	35.0	Unknown	Unknown
maven/org.geotools:gt-excel-writer	35.0	Unknown	Unknown

Scanned Files

• pom.xml

[github-actions]

Test Results

639 tests  +639   636 ✅ +636   2h 57m 28s ⏱️ + 2h 57m 28s
 59 suites + 59     1 💤 +  1 
 59 files   + 59     2 ❌ +  2 

For more details on these failures, see this check.

Results for commit 76c9d0f. ± Comparison against base commit 9f86afc.

♻️ This comment has been updated with latest results.

[Copilot]

Pull request overview

This PR upgrades the project to GeoTools 35.0 and restores GeoJSON as a supported extract output format, while also hardening/adjusting GeoTools XML entity resolution to keep local-entity blocking in place but allow GeoServer-style dynamic DescribeFeatureType schema requests.

Changes:

• Bump GeoTools dependency version to 35.0 and (re-)enable GeoJSON extract output via default configuration.
• Add TMPreventLocalEntityResolver and initialize GeoTools on startup with this preferred resolver.
• Re-enable the GeoJSON extract integration test that previously depended on newer GeoTools behavior.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
pom.xml	Updates GeoTools version property to 35.0.
src/main/resources/application.properties	Adds geojson to allowed extract output formats.
src/test/resources/application.properties	Mirrors allowed extract output formats update for tests.
src/main/java/org/tailormap/api/geotools/TMPreventLocalEntityResolver.java	Introduces a custom entity resolver to permit specific DescribeFeatureType requests.
src/test/java/org/tailormap/api/geotools/TMPreventLocalEntityResolverTest.java	Adds unit tests covering allowed/blocked resolver behaviors.
src/main/java/org/tailormap/api/geotools/featuresources/WFSFeatureSourceHelper.java	Configures WFS datastore to use the custom resolver.
src/main/java/org/tailormap/api/configuration/GeoToolsConfiguration.java	Initializes GeoTools with preferred hints/resolver at application startup.
src/test/java/org/tailormap/api/controller/LayerExtractControllerIntegrationTest.java	Re-enables the GeoJSON export integration test by removing @DisabledUntil.

[codecov]

❌ 2 Tests Failed:

Tests completed	Failed	Passed	Skipped
705	2	703	1

View the full list of 2 ❄️ flaky test(s)

org.tailormap.api.controller.admin.GeoServiceAdminControllerIntegrationTest::check_cors_header_is_saved

Flake rate in main: 5.56% (Passed 17 times, Failed 1 times)

Stack Traces | 5000s run time

Status expected:<201> but was:<400>

org.tailormap.api.controller.admin.GeoServiceAdminControllerIntegrationTest::refresh_capabilities

Flake rate in main: 5.56% (Passed 17 times, Failed 1 times)

Stack Traces | 5000s run time

Status expected:<201> but was:<400>

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}