Changelog for xmlresolver-javadoc-5.2.0-3.7.noarch.rpm :

* Fri May 19 2023 shvetz.antonAATTgmail.com- Update to v5.2.0
* Changes of version 5.2.0: = Add a new API for constructing a catalog directly from a stream of SAX events. This makes it possible to construct a catalog directly from a database, for example, or from a novel format.
* Changes of version 5.1.3: = Fixes a small bug wherein same document references were not handled correctly if the ALWAYS_RESOLVE feature was true.
* Fri Apr 14 2023 shvetz.antonAATTgmail.com- Update to v5.1.2
* Changes of version 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.- Remove build dependency on mvn(xml-apis:xml-apis).
* Sun Mar 05 2023 shvetz.antonAATTgmail.com- Update to v5.1.1
* Changes of version 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.
* Changes of version 5.1.0: = Fixes a significant bug in the new ALWAYS_RESOLVE feature. See #133
* Changes of version 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.
* Thu Jan 26 2023 shvetz.antonAATTgmail.com- Update to v4.6.4
* Changes of version 4.6.4: = 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.
* Fri Nov 25 2022 shvetz.antonAATTgmail.com- Update to v4.6.0
* Changes of version 4.6.0: = 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).
* Changes of version 4.5.2: = Make CatalogResolver.{resource,uncachedResource} protected by AATTndw in #119 = Encode (but don\'t double-encode) catalog filenames by AATTndw in [#120] = Make sure that the catalog DTDs are resolved locally by AATTndw in #121
* Changes of version 4.5.1: = This release fixes #113, public identifier values in the catalog were not being normalized.
* Changes of version 4.5.0: = The only significant change in this release is that the cache is disabled by default.
* Mon Aug 01 2022 shvetz.antonAATTgmail.com- Update to v4.4.3
* Thu May 05 2022 shvetz.antonAATTgmail.com- Initial packaging with v4.3.0