On Fri, Apr 30, 2004 at 11:28:45AM +0200, Hussein Shafie wrote: > >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?). I think this is more than would be required. I simply would like to have URI resolving whenever URIs are used (within a given application, in this case, XXE). My use case is as follows. I have an XSLT script which imports another XSLT script by URI (say with <xsl:import href="http://some.where.net/script.xsl"/>). This script is used in an XXE configuration. The configuration also contains a local cache of the global, imported XSLT script and an XML catalog that uses the uri element (say with <catalog:uri name="http://some.where.net/script.xsl"; uri="xsl/script.xsl"/>) to redirect references from the global URI to the local cached copy. I don't think this requires any sort of identification of the resource at the URI. You only redirect names in an XML catalog. > 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 my description above is not enough, let me know. > You are never too vague. Is this sarcasm? :) Take care, John L. Clark -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20040430/b0337a48/attachment.sig
