dom tree vs. xslt processor tree - what is the difference? -


Since DOM is represented by a tree of XML and XSLT processors, using the paste structure as their input, I think What was the difference between the structure of DOM and tree of an XSLT processor? And how can XSLT processor like Saxon be implemented on SX? Does this mean that it generates input tree structure from SAX reports? Is not it a bit cumbersome? Why do some things that do not already provide a tree structure?

Since DOM is a tree representing XML,

When you can use DOM with XML, then DOM is often represented by a tree of HTML

and XSLT processors use the tree structure as their input, < / P>

When I use saxon on the command line, then I get it a file. It is a sequence of bytes, the tree is not something to change this sequence into a tree.

I was wondering what is the difference between structure of DOM and XSLT processor tree?

List all the differences will be very long, but some major topics: they have a public interface, trees used by the XSLT processor do not have to conform to any standard. An XSLT processor can very well create its own tree, which is designed to be used only for its own purposes.

  • DOM trees are generally structurally mutual. The tree used for XSLT processing can be structurally unstable but is usually used instantly ("structurally ineligible" I am talking about adding, removing elements, and extending surrounding elements. There is no facility in XSLT to modify the input as it is processed.)

  • DOM tree support things that are not understood in XSLT processing For events, event handlers.

    How can XSLT processors like Saxon be implemented on SACX? Does this mean that it generates input tree structure from SAX reports? Is not it a bit cumbersome? Why do not it already provide a tree structure?

    Yes, an XSLT processor will use the incidence of SAC to generate a tree for internal processing. (And what does succession do.) There are good reasons that SAC can use a library instead of producing a custom tree that builds the Dom Tree. Earlier I had said that XSLT processors usually use their tree structurally irreversibly. This optimization may allow that a DOM implementation may not be able to execute. Here is an example if your tree is structurally irreversible, you can calculate the list of elements of a node for once and for all. It can never change after calculation, however, in a dom tree, the list of element of the node can change because the tree is unstable, so that you can handle changes The provision is that custom paste does not have to support things that do not make emotions for XSLT processing, such as an event of such type of optimization can have applications that take less memory and run faster.

  • Comments

    Popular posts from this blog

    php - PDO bindParam() fatal error -

    logging - How can I log both the Request.InputStream and Response.OutputStream traffic in my ASP.NET MVC3 Application for specific Actions? -

    java - Why my included JSP file won't get processed correctly? -