Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Date: Thu, 25 May 2000 09:27:57 -0500
From: Mike Engelhart <mengelhart@earthtrip.com>
Subject: XSP confusion
To: Cocoon Dev <cocoon-dev@xml.apache.org>
Message-id: <B552A29D.9E50%mengelhart@earthtrip.com>
MIME-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022

Hi all -

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?

Any thoughts??