DOCBOOK-APPS: Xalan 1.0.1 crashing with DocBook XML v4.0 and DocBook XSL v1.13

[Steven Maring <Steven dot Maring at trcinc dot com>]

[Note: I approved this message to docbook-apps, not docbook]

I don't know if this is caused by Norman Walsh's XSL or something in Xalan.
But it sounds like it is having a problem with an entity reference.

When I take a simple docbook xml file like:

<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.0//EN" 
    "http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd">
<article>
  <artheader>
    <title>My Article</title>
    <author><firstname>Steven</firstname><surname>Maring</surname></author>
  </artheader>
  <section>
    <title>Summary</title>
    <para>Foo bar foo bar..</para>
  </section>
</article>

and XML parse(w/ Xerces 1.1.1) and XSL process it against the DocBook XSL
v1.13 .../xhtml/docbook.xsl like so:

DOMParser parser = new DOMParser();
parser.setFeature("http://xml.org/sax/features/validation", true);
parser.parse( xmlFile );
Document document = parser.getDocument();

FileReader xslFileReader = new FileReader( xslFile );
InputSource xslInputSource = new InputSource( xslFileReader );
XSLTProcessor processor = XSLTProcessorFactory.getProcessor();
processor.process( new XSLTInputSource( document ), 
                   new XSLTInputSource( xslInputSource ), 
                   new XSLTResultTarget( System.out ) );

I get:

file:/html/docbook.xsl; Line 0; Column 0
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.xerces.framework.XMLParser: method
getSystemId()Ljava/lang/String; not found
	at
org.apache.xalan.xpath.xdom.XercesLiaison.parse(XercesLiaison.java:285)
	at
org.apache.xalan.xslt.XSLTEngineImpl.parseXML(XSLTEngineImpl.java:887)
	at
org.apache.xalan.xslt.StylesheetHandler.processInclude(StylesheetHandler.jav
a:1348)
	at
org.apache.xalan.xslt.StylesheetHandler.startElement(StylesheetHandler.java,
Compiled Code)
	at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java,
Compiled Code)
	at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidat
or.java, Compiled Code)
	at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanne
r.java, Compiled Code)
	at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
LDocumentScanner.java, Compiled Code)
	at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java, Compiled Code)
	at org.apache.xerces.framework.XMLParser.parse(XMLParser.java,
Compiled Code)
	at
org.apache.xalan.xpath.xdom.XercesLiaison.parse(XercesLiaison.java:272)
	at
org.apache.xalan.xslt.XSLTEngineImpl.processStylesheet(XSLTEngineImpl.java:7
15)
	at
org.apache.xalan.xslt.XSLTEngineImpl.process(XSLTEngineImpl.java:556)
	at XSLTransform.main(XSLTransform.java:34)

Norman suggested that Xalan might be a little flakey on his sight: "In my
tests Xalan (1.0.1) behaved a little badly, but I think that's related to
Xalan, not my markup."

Anybody had success with this?

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
|  Steve Maring
|  Web Application Engineer
|  Technical Resource Connection, Inc.
|  smaring@trcinc.com
|  813-891-6084 x4323
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-