On Thursday, Nov 7, 2002, at 16:19 Europe/London, Joerg Heinicke wrote:
normally this won't work. You create a Result Tree Fragment in
$colours and have to convert it to a node set using node-set()
extension function. This is not possible when using XSLTC.
Sorry for the red-herring!
I did n
On Wednesday, Nov 6, 2002, at 21:26 Europe/London, Stephen Ng wrote:
I say,
document() is good for rapid prototyping, but is a poor choice for
final deployment for performance reasons. Use aggregation instead.
The Cocoon developers recommend to use aggregation or
xinclude because of SoC (XSLT
> > I say,
> > document() is good for rapid prototyping, but is a poor choice for
> > final deployment for performance reasons. Use aggregation instead.
>
> The Cocoon developers recommend to use aggregation or
> xinclude because of SoC (XSLT is for transforming, not for
> aggregating content).
#setURIResolver(javax.xml.
transform.URIResolver)
> -Original Message-
> From: Ilya A. Kriveshko [mailto:ilya@;kaon.com]
> Sent: 05 November 2002 14:33
> To: [EMAIL PROTECTED]
> Subject: Poor performance of document() in XSL [Was: Re: simpel cocoon
> question]
>
>
> SAX
SAXESS - Hussayn Dabbous wrote:
But you also could do it directly within the xslt context:
You can use the document() function in your XSLT-file.
This function allows you to refer to data contained within
another XML-file. This is completely decoupled from cocoon
though. It's more about how to w
