Norman Walsh
Norman Walsh
Yes. I think we should be able to do better here. The whole tangled mess of URI-related/resolver-related APIs is a mess.
Indeed, the problem with the unparsed text resolver is clearly my fault. Here's a sketch of a proposal for a new design. Comments most welcome: https://so.nwalsh.com/2023/08/29-xmlresolver
You can (and I would really appreciate it if you did!) try them out now: [6x-SNAPSHOT](https://xmlresolver.org/6x-snapshot/)
Radu Coravu ***@***.***> writes: > @ndw sorry, we are getting close to a release, found some time to look a bit into this. This link > you mention in your...
This is now shipping in the 6.x resolver, so I'm going to close this. The tl;dr is, I think, that you can provide your own extension of the `XMLResolver` class...
That's fair. The implementation produces `.class` files that are compatible with Java 8. That's the point that has historically been most important to library users, but the description should definitely...
Thanks. I'm not actually sure how to change that. I don't see any reference to that URI in the Sonatype metadata...???
I've got an open support request with the Sonatype folks trying to get this sorted out.
I believe your analysis is correct. The `SchemaFactory` doesn't attempt to use the resolver for the initial URI, so there's nothing the resolver can do to resolve it locally. If...
I'll try to look next week. (I'll have a few hours each morning before Balisage begins.) There's almost no chance I can look at this before then.