6.0.9

XML Resolver 6.0.9 released

6.0.8

Restores the NamespaceResolver API. This API, like the other shims for 5.x backwards compatibility, is deprecated, but it does make version 6.0.8 a better drop-in replacement for version 5.x.

6.0.7

Removes two external dependencies. This makes the 6.x resolver release a drop-in replacement for the 5.x release in most cases.

6.0.6

This is a maintenance release of the 6.0.x resolver, which is still in "beta".

The following changes are included:

• Improvements to support for UNC paths

  Documents and catalogs that use Windows UNC paths are better supported if the FIX_WINDOWS_SYSTEM_IDENTIFIERS feature is enabled.

• Support for Java 21

  The build still produces class (and jar) files that will work with any version of Java back to Java 8. However, the build itself now uses Java 21. This closes issue #173.

• Refactor the SAX entity resolvers

  The SAX EntityResolver and EntityResolver2 interfaces are now implemented on separate objects. This closes issue #183.

• Fix namespace-based lookup in the DOM

The LSResourceAdapter API used when resolving documents for the DOM did not correctly handle XML Schema validation. It was failing to lookup based on the namespace. This closes issue #180.

• Improved support for concurrency

  The catalog lookup code was not sufficiently careful about multi-threaded access. My thanks to JFK-DXML for the patch. This closes issue #182.

• Reworked the FIX_WINDOWS_SYSTEM_IDENTIFIERS feature

  This feature now applies irrespective of platform. This will enable Windows documents and catalogs to work correctly even on non-Windows systems. This closes issue #184.

A number of smaller issues (testing and build system issues and issues not expected to be user visible) have also been corrected. See the commit log for more details.

5.2.5

This is a maintenance release of the 5.x resolver.

The following changes are included:

• Fix namespace-based lookup in the DOM

  The LSResourceAdapter API used when resolving documents for the DOM did not correctly handle XML Schema validation. It was failing to lookup based on the namespace. This closes issue #180.

• Improved support for concurrency

  The catalog lookup code was not sufficiently careful about multi-threaded access. My thanks to JFK-DXML for the patch. This closes issue #182.

A number of smaller issues (testing and build system issues and issues not expected to be user visible) have also been corrected. See the commit log for more details.

5.2.4

This is a maintenance release to fix a Windows-only bug related to attempting to resolve documents with "Windows path" URIs, that is, invalid URIs with backslash characters in them.

The bug (#184) was that when the URI wasn't resolved via the catalog and the resolver attempted to open the URI directly to return it, the backslashes weren't fixed and java.net.URI threw an exception. That's been fixed.

I've also changed how the FIX_WINDOWS_SYSTEM_IDENTIFIERS feature is interpreted. It's now treated the same on all platforms where it was previously ignored on non-Windows platforms.

These fixes have also been applied to the "v6" code on the main branch, but I have a number of other bugs to sort out before I can make a new release there.

6.0.4

XML Resolver 6.0.4 released

6.0.3

This release introduces (deprecated) APIs that implement some of the most common features from the V5.x APIs. This should allow version 6.x to substitute for version 5.x until dependent libraries can be updated.

It also fixes a bug where classpath: URIs were not being masked.

6.0.2

XML Resolver 6.0.2 released

6.0.1

This release fixes a bug in 6.0.0 that introduced a compile-time dependency on every resolver API implemented by XMLResolver, even APIs not actually used by the application. This has been resolved by adding adapter classes.