Databases
StackOverflow2013
Postsdbo
POWhen I parse an XSLT in a context where the input and output are SAX, is a DOM tree created behind the scenes?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhen I parse an XSLT in a context where the input and output are SAX, is a DOM tree created behind the scenes?
    primarykey
    data
    text
    <p>Here is example code I am referring to:</p> <p><a href="http://xml.apache.org/xalan-j/usagepatterns.html#sax" rel="nofollow">http://xml.apache.org/xalan-j/usagepatterns.html#sax</a></p> <p>First, notice that everything that can be SAX-based is SAX-based in this code: both the input and the output.</p> <p>Also, notice that a transformerHandler object is created off of "foo.xsl" and that transformerHandler is used to do a transformation from the SAX input to the SAX ContentHandler that creates the output.</p> <p>I had understood that XSLT requires something like a DOM tree to be built in order for it to do its work.</p> <p>So here is my question: I wonder if the transformerHandler is actually building something like a DOM tree behind the scenes? If it is, doesn't that kind of defeat the purpose of trying so hard to stay in SAX-land?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDimitre Novatchev
    1. USBPS
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI found this: [http://xml.apache.org/xalan-j/dtm.html](http://xml.apache.org/xalan-j/dtm.html) which seems to suggest that they use something like VTD-XML behind the scenes. This is much more efficient than a DOM tree and makes sense in the context. I'll leave this up for a while and see if anyone else comes up with a more definitive answer.
      singulars
      1. POWhen I parse an XSLT in a context where the input and output are SAX, is a DOM tree created behind the scenes?
      1. USBPS
    2. COIt is done in one phase - you do not get access to the process while it is runing. The point was, that it requires a new instatiation, for every new document. When I do this NOT using SAX, I can (re)use the same processor over and over. If you already have a DOM instance, this can be parsed, like a prepared input - it will save some overhead - because it does not need to do a parse from META to DOM
      singulars
      1. POWhen I parse an XSLT in a context where the input and output are SAX, is a DOM tree created behind the scenes?
      1. USMike
    3. COIt all depends on the stylesheet and the transformer internal implementation (how many clever optimizations the author(s) managed to squeeze in to it). I refer to this article, http://www.ibm.com/developerworks/library/x-xslt2/, about the internal design of an early Saxon. If you read it I think you will appreciate that "staying in SAX-land" can be beneficial.
      singulars
      1. POWhen I parse an XSLT in a context where the input and output are SAX, is a DOM tree created behind the scenes?
      1. USforty-two
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload