so

Catalog resolver migration

Volume 4, Issue 39; 07 Aug 2020

Migrating your application from the Apache Commons catalog resolver to XML Resolver.

I’ve written about the XML Resolver project a few times (I pushed 1.0.0 in March of last year and I wrote about the 1.0.6 release in December; the current release is 1.0.8). The XML Resolver is my reimplementation of the catalog resolver for JVM applications.

It uses the OASIS XML Catalogs V1.1 Standard to provide a mapping from public identifiers and URIs to local resources. The URIResolver, EntityResolver, EntityResolver2, NamespaceResolver, and LSResourceResolver interfaces are all implemented. It also supports automatically caching downloaded resources so that they’re available locally the next time.

One question that arises from time to time is “how do I migrate to the new resolver”? The answer is, basically, change one or two class names. You’re done.

I’ve attempted to demonstrate this in a new repository, https://github.com/ndw/resolver-migration that includes both documentation and code samples.

It’s a little hard for me to predict all the ways that developers might have integrated catalog support into their applications. If you’re trying to migrate and can’t figure out how, open an issue and I’ll see if I can help.

Please provide your name and email address. Your email address will not be displayed and I won’t spam you, I promise. Your name and a link to your web address, if you provide one, will be displayed.

Your name:

Your email:

Homepage:

Do you comprehend the words on this page? (Please demonstrate that you aren't a mindless, screen-scraping robot.)

What is ten minus three?  (e.g. six plus two is 8)

Enter your comment in the box below. You may style your comment with the CommonMark flavor of Markdown.

All comments are moderated. I don’t promise to preserve all of your formatting and I reserve the right to remove comments for any reason.