Bug #3474
closed
Catalog not used in sourceLocation of packages in configuration files
0%
Description
I use a xml catalog file with entries like this :
<rewriteURI uriStartString="myPrefix:/" rewritePrefix="file:/[path-in-filesystem]/"/>
When I use, the following instruction in a xsl, catalog is used, and the referenced xsl is found :
<xsl:include href="myPrefix:/my-xsl.xsl"/>
But when I use the same in a saxon's configuration file that declares packages, it doesn't work :
<xsltPackages>
<package name="my URI" version="1.0" sourceLocation="myPrefix:/lib/my-package.xsl"/>
</xsltPackages>
It act as catalogs are not used in the uri resolution of packages. Following error is raised :
I/O error reported by XML parser processing myPrefix:/lib/my-package.xsl: unknown protocol: myPrefix
If I use absolute or relative (to conf. file) URI it's OK.
Possible to fix it ?
Thanks
Updated by Michael Kay over 6 years ago
How many levels of indirection do you need? I would have thought having a mapping from package names to package locations in the configuration file gave you quite enough flexibility, without having another level of indirection through an OASIS catalog.
Updated by Arnaud Malguy over 6 years ago
Perhaps I could do otherwise, I just wonder if I could use the same method everywhere. It will add consistency into my application. Easier for me
but my application should perhaps do otherwise.
Anyway congratulations for the packages, it' awesome.
Updated by Michael Kay over 6 years ago
- Status changed from New to Rejected
Decided that the product is working as designed. We don't see a need for another level of indirection here: the additions in the configuration file are intended to map package names / versions to actual locations, not to locations that need to be further resolved using an OASIS catalog.
Please register to edit this issue
.