cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ricardo Rocha <>
Subject Re: XSP confusion
Date Thu, 25 May 2000 15:01:15 GMT
Mike Engelhart wrote:
> Ricardo's announcement that the XSP engine in Cocoon 2 is DOM based while
> the rest of Cocoon 2 is SAX based has left me with some design questions.  I
> was planning on making all the code in my application use XML directly
> (either DOM or SAX depending on what Cocoon 2 was going to use which I
> assumed was SAX) rather than using XSP to generate the XML from existing
> Java objects (e.g., iterating through a ResultSet or ArrayList, etc).
> It seems from a performance standpoint, SAX is the way for me to go but does
> this mean that I have to generate DOM objects every time I want to put an
> XML element or fragment into an XSP dynamically?

XSP uses DOM _internally_ (i.e. for code generation purposes only), but
generated classes are SAX-based. Thus, whenever you need to put an XML
or fragment you'll use SAX, not DOM.



View raw message