Thanks for your suggestions, Andy.
If you (or anyone else) have already worked with custom resolvers for 3rd
party libraries in Java, feel free to pass me on examples. They might help
us to provide support for xmldb: or basex: URI schemes.
Andy Bunce schrieb am Di., 25. Sep. 2018, 14:38:
>
Ok, Thanks for the info it is what I guessed, but I note the "currently" :)
It would be good, long term, to look to matching the Saxon capabilties here
[1], part of which (xslt) are covered by this issue [2].
And related: I wonder sometimes about a "xmldb:" uri scheme and a custom
resolver that
Hi Andy,
Currently, XML catalog files will only be evaluated by the XML parser,
which will be called after the addressed resource has been located and
retrieved. In other words: The specified catalog file will be
evaluated indeed, but only for URIs that occur within the specified
XML document:
Hi,
Using a recent 9.1 Beta on windows.
I create an XML catalog at c:\tmp\mycatalog.xml
http://nowhere.com/doc;
uri="file:///c:/tmp/doc.xml" />
Then in the GUI
fetch:xml("http://nowhere.com/doc;,
map{"catfile": "C:\tmp\mycatalog.xml"}
)
It goes to nowhere, I was hoping to get back
4 matches
Mail list logo
