Ebner, ZG 8640, BN wrote: > XXE didn't show my catalog in it's About dialog. But - that doesn't mean it > didn't use it: If I modify another entry in the catalog, it get's noticed. > > Here's my catalog: > ################################################ > <?xml version='1.0' encoding='UTF-8'?> > <!DOCTYPE catalog > PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" > > "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd";> > <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog" > prefer="public"> > <public > publicId="-//OASIS//DTD DocBook XML V4.3//EN" > uri="file:///d:/docbook/dist/docbook/docbookx.dtd"/> > <system > systemId="file:///C:/Programme/docbook/xml/4.3/xinclude.mod" > > uri="file:///D:/docbook/dist/dpag/xml/xinclude.mod"/> > <rewriteURI > rewritePrefix="file:///D:/docbook/dist/work/" > uriStartString="local://"/> > </catalog> > ################################################ > If I change the system entry into something which can't be resolved, XXE > complains about it! > > BTW: xmllint and xsltproc are using the same catalog without any warning.
Strange! Thanks for the feedback. We didn't know that. In XXE, support of XML catalogs is implemented using http://xml.apache.org/commons/components/resolver/index.html, which is a library of classes written in Java[tm] (by Norman Walsh, I think). To my knowledge, xmllint/xsltproc is written in C; that's why XXE and xsltproc don't behave the same when dealing with XML catalogs.
