Fixes a small bug wherein same document references were not handled correctly if the ALWAYS_RESOLVE feature was true.
5.1.2
This release removes the (transitive) dependency on the xml-apis jar file. There's also one new log message for tracking catalogs that are loaded.
5.1.1
Enforce ACCESS_* features when opening connections
The new ALWAYS_RESOLVE feature means that the resolver will sometimes access resources on behalf of the caller (ones that were not found in the catalog). That feature failed to take the ACCESS_EXTERNAL_DOCUMENT and ACCESS_EXTERNAL_ENTITY features into consideration.
5.1.0
The 5.1.0 release fixes a significant bug in the new ALWAYS_RESOLVE feature. See #133
5.0.0
The Java contract for the entity resolver is to return null if the entity isn't found. Unfortunately, redirects are common these days (for example, w3.org redirects all http: URIs to https: URIs) and parsers don't always follow redirects, so if the resolver returns null, the parse fails. That's...suboptimal.
This release adds a new feature ResolverFeature.ALWAYS_RESOLVE that will resolve the resource (and follow redirects to do so) and always return it. This feature is true by default.
This release also extends the ResolverInputSource to expose the response code (if applicable) and headers (if available) from the response.
4.6.4
What's Changed
Fixed #126 where an input document without a base URI (e.g., one with a null systemId) would cause an NPE
Fixed #127 where attempting to parse a RDDL document wasn't following redirects
Fussed with the CI process. There was no 4.6.1, 4.6.2, or 4.6.3 published release.
The W3C now redirects http: URIs to https: URIs, so you can't load namepace documents unless you follow redirects.
4.6.0
This release contains two changes:
I've fixed the bug where a catalog.xml file on the classpath (if the classpath pointed to a directory, for example) would not be loaded.
It's now possible to set properties with either Java system properties or environment variables. (There are places where it's tricky to set system properties, and the C# version already supported environment variables, so it seemed reasonable).
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
1 year ago
Bumps xmlresolver from 2.1.1 to 5.1.3.
Release notes
Sourced from xmlresolver's releases.
... (truncated)
Commits
65b0071Merge pull request #141 from ndw/iss-140ad9c83cBump versionc959cc2Handle same-document references correctly8f7efb8Merge pull request #139 from ndw/remove-xml-apis7ab1695Bump version62f3a59Exclude redundant xml-apis jar17a71baAdd debugging message to track catalogs loaded0adc820Merge pull request #138 from ndw/iss-137be1e28fBump version43c67a0Enforce ALLOW_* when accessing resources, fix #137Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)