W. Eliot Kimber wrote:
1. Is my analysis correct or have I missed some easy way to return this
markup?
2. If my analysis is correct, does anyone have an example of doing this
sort of off-the-cuff SAX processing I could crib from? I didn't find any
examples in the Saxon-supplied samples.
My analysis is correct--turns out one of my collegues had already
figured this out and I didn't know it. What I had missed was the the
"Parse()" method on the Saxon DocumentBuilderImpl class, which allows
you to pass in a string to be parsed more or less directly. Here's the
basic pattern:
public NodeInfo generateResultTree(String markup) {
java.io.ByteArrayInputStream bais = new
ByteArrayInputStream(markup.getBytes());
org.xml.sax.InputSource isource = null;
try {
isource = new InputSource(bais);
} catch (org.xml.sax.SAXException e) {
e.printStackTrace();
}
org.w3c.dom.Document root = new
com.icl.saxon.om.DocumentBuilderImpl().parse(isource);
return (NodeInfo)(root.getDocumentElement());
}
Cheers,
--
W. Eliot Kimber, eliot(_at_)isogen(_dot_)com
Consultant, ISOGEN International
1016 La Posada Dr., Suite 240
Austin, TX 78752 Phone: 512.656.4139
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list