Skip to content

using GT utility classes for XML parsing/producing#1533

Closed
pmauduit wants to merge 2 commits into
GeoWebCache:mainfrom
pmauduit:default-entity-resolver-check
Closed

using GT utility classes for XML parsing/producing#1533
pmauduit wants to merge 2 commits into
GeoWebCache:mainfrom
pmauduit:default-entity-resolver-check

Conversation

@pmauduit
Copy link
Copy Markdown

See related PRs on GT/GS for the motivation:

Making use of GT utlity class to get XML-parsing related objects so that they are obtained from a centralized source.

@pmauduit pmauduit force-pushed the default-entity-resolver-check branch from ce886b9 to a09bfd8 Compare May 22, 2026 10:19
@pmauduit pmauduit force-pushed the default-entity-resolver-check branch from a09bfd8 to ca48939 Compare May 22, 2026 10:21
@jodygarnett
Copy link
Copy Markdown
Contributor

Hi @pmauduit I would like to merge to default-entity-resolver-check so that the upstream GeoTools integration tests can run.

With that in mind I will cherry pick your two commits over to that branch.

Q: Do you have access to geowebcache repo to work on public branch?

@pmauduit
Copy link
Copy Markdown
Author

I'm missing 2 places in the code where I could not use GT's XMLUtils, I don't have access to GWC, so the current pr has been opened from my fork.

@jodygarnett
Copy link
Copy Markdown
Contributor

This PR is supersseded by #1534 which makes use of public default-entity-resolver-check branch which is subject to integration tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants