Project

Profile

Help

EntityResolver in .xsl vs .xml

Added by Brian Tusi over 11 years ago

Hello. First off, apologies if this is related to https://saxonica.plan.io/boards/3/topics/5507 -- I'm admittedly a bit naive when it comes to XSL in Java.

We're using the latest Saxon, version 9.4.0.7. We have a simple XML document:



  %lat1;
]>

and a simple XSL stylesheet:



  %lat1;
]>



  Content was here.



These documents are processed with Saxon with the following command:

java -jar saxon9ee.jar -t -s:bare.xml -xsl:bare.xsl

If we remove the DOCTYPE from the XSL stylesheet, the .ent file is fetched internally from Saxon, and everything works quickly and smoothly. However, if we keep the DOCTYPE in the XSL document as-is, the output is incredibly delayed, and I can see through tcpdump that an HTTP call to w3.org is being performed. During both runs, the output does say "Fetching Saxon copy of w3c/xhtml-lat1.ent", but there is a long pause (if the DTD is specified) between the "Using license serial number" and "Generating byte code" lines.

Should the built-in StandardEntityResolver work for both the XML and XSL documents, or is there something different that needs to be done?


Replies (1)

RE: EntityResolver in .xsl vs .xml - Added by Michael Kay over 11 years ago

Thanks for reporting it. I've logged it here:

https://saxonica.plan.io/issues/1727

and have tested a patch.

    (1-1/1)

    Please register to reply