Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Conal Tuohy" <conalt@paradise.net.nz>
To: "Cocoon Users (E-mail)" <cocoon-users@xml.apache.org>,
	"Cocoon Developers (E-mail)" <cocoon-dev@xml.apache.org>
Subject: xt:document in cocoon?
Date: Fri, 5 Apr 2002 11:34:59 +1200
Message-ID: <001c01c1dc31$56d48100$d9784fcb@insurgentes.local>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal

I have some questions about using the XT extension "document" in Cocoon.

This feature allows an XSLT to produce multiple output documents; it's often
used (outside of Cocoon) to produce a collection of small web pages from a
large source file. I have access to some XSLT code which does this, which
I'd like to use in Cocoon.

It seems to me, though, that this implies a kind of "batch-processing"
paradigm, and that Cocoon (being part of an http server), is more suited to
having XSLT files that produce a single output document (returned to the
user's browser). If xt:document is at all useful in Cocoon, it would be e.g.
to take data posted from an HTML form and save it to the disk from within an
XSLT.

What do others think? Am I right? Am I best to hack the XSLT code I have
which uses xt:document? Has anyone else had to do something similar?

BTW, I notice that in XSLT 1.1 the W3C intended to make this feature
standard, but XSLT 1.1 was abandoned, and the feature has been removed from
the XSLT 2 Requirements document http://www.w3.org/TR/xslt20req


---
Conal Tuohy
conalt@paradise.net.nz


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org