These can be tricky to debug. Are you seeing a trace of URI requests from the catalog resolver? If not, have you tried using a monitoring tool such as Wireshark?
The normal cause of problems is that a source file contains a DTD or schema reference to files hosted on www.w3.org. These requests will fail immediately if there is no network, and they will usually fail after a 30 second delay if there is a network, because W3C (since a couple of years ago) has been throttling requests to serve these files. Recent versions of Saxon deal with this by automatically redirecting requests to a local copy held within Saxon itself, but with earlier releases (including 9.1.0.8) the redirection has to be done at user level. This is all several levels removed from Saxon itself: Saxon calls the XML parser (usually Xerces) to do the parsing, and requests for DTDs etc emanate from the parser, not from Saxon. So Saxon doesn't actually know what files are being requested. Regards, Michael Kay Saxonica On 9 Jan 2014, at 08:17, Mathieu Malaterre <ma...@debian.org> wrote: > Dear Mike, > > I am trying to solve issue reported against debian: saxonb 9.1.0.8 > package. The full report is at: > > http://bugs.debian.org/567210 > > In summary the documentation from: > > http://www.saxonica.com/documentation/sourcedocs/xml-catalogs.html > > Does not seems to apply when used within debian installation. Indeed > if one download the testcase from: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567210#10 > > and run: > > $ java -cp > /etc/xml/resolver:/usr/share/java/xml-resolver.jar:/usr/share/java/saxonb.jar > -Dxml.catalog.files=/etc/xml/catalog -Dxml.catalog.verbosity=1 > net.sf.saxon.Transform -x > org.apache.xml.resolver.tools.ResolvingXMLReader -y > org.apache.xml.resolver.tools.ResolvingXMLReader -r > org.apache.xml.resolver.tools.CatalogResolver -s:foo.xml -xsl:foo.xsl > > I always get an error without network, however it seems to be doing > something else when network is up. I have not been able to track down > what is actually missing during this XSLT transform. > > The file /etc/xml/resolver/CatalogManager.properties comes from > libxml-commons-resolver1.1-java package. > > Could you please let me know if there is a way to debug (log) what is > actually downloaded from the net that makes this test script fails. > > Thanks much in advance, -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
