John L. Clark wrote: > I was simply wondering if XXE (and XFC) perform XML catalog resolution > on URIs from xslt:include statements in XSLT scripts. I have an XXE > configuration that contains an XSLT script which includes a global > external XSLT script, contains the associated XXE command, and contains > a bundled xml catalog that resolves the global reference to a local > copy. However, XXE is failing with a: > > Error: Failure reading <Global URI> > > error in its log. This makes me question whether it is looking up the > URI reference in the catalog collection. > > I have also tried to load the stylesheet into XFC (xslutility) and > configure XFC to make use of the same catalog for resolving that > reference, and I get the same error. > > Does XXE only use XML catalogs for its internal resolution?
XXE currently uses XML catalogs for the resolution of DTDs and external entities. This resolution happens when the document is being loaded. > If so, is there any way to pass XXE's catalog information on to the XSLT > processing engine? Currently no. Technically, it is very easy to use an URI resolver for the XSLT style sheet and we could add this feature very easily. The problem is: we have not taken the time (i.e. we are lazy) to explore all the functions of XML catalogs and we simply don't know how to specify an entry for an XSLT style sheet in an XML catalog (example: what is the public ID of an XSLT style sheet?). Sending us an example of such XML catalog, with a reference on the Web explaining why your specific use of XML catalogs is legal, would help us. > If I am being too vague, here, I can provide a test configuration which > exhibits this problem. You are never too vague.
