Subject: XSL and the DOM From: "Jon Smirl" <jonsmirl@xxxxxxxxxxxx> Date: Thu, 21 Oct 1999 15:12:53 -0400 |
I would like to be able to construct a DOM tree of my input document and then pass it into an XSL processor. I would also like to use XPath to query this tree as it is constructed. I checked several XSL processors and none seem to support this. This is probably because of namespace and XPath issues. I then went and read the DOM2 spec which makes no mention of XPath. Why is this, shouldn't XPath be part of DOM2? Right now all of the XSL processors are taking SAX events and building their own DOM trees with their own APIs. Could this be split out in standard manner if the DOM supported namespaces and XPath? In my server-side app I currently build DOM1 trees and then convert them into SAX events to drive the XSL processors. There should be a better way. Jon Smirl jonsmirl@xxxxxxxxxxxx XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: XSL FOs -> PDF using InDesign, Nikolai Grigoriev | Thread | Re: XSL and the DOM, zun |
Re: XSL FOs -> PDF using InDesign, Sebastian Rahtz | Date | ANN: 4XPath 0.7.2, uche . ogbuji |
Month |