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
Hello, Joerg;
thank you very much for the info.
The other solution is indeed much nicer, and much easier to
understand than mine ;-)
regards, hussayn
Joerg Heinicke wrote:
Hello Hussayn,
the question was also on the XSL list yesterday and there is a simpler
solution:
http://www.biglist.com/l
Hello Hussayn,
the question was also on the XSL list yesterday and there is a simpler solution:
http://www.biglist.com/lists/xsl-list/archives/200211/msg00188.html
Furthermore version="1.1" is only supported in pre-implementations of Saxon.
XSL 1.1 died in Working Draft status.
Regards,
Joerg
Hy;
The stylesheet below will do it. The trick is recursively
calling the template "project-measure".
I would be interested, if there is a more elegant/efficient
way, doing this in xslt or inside of cocoon ...
regards, hussayn
http://www.w3.org/1999/XSL/Transform";
version='1.1'>
Thanks for the hints, aggregation is the way to go for sure, but im still
facing a problem
Basicly what im looking for is how to (fastest possible way) do to a project
(relational algebra) operation on a long list of relations in xsl.
Im not sure this should be done in xsl perhaps I need a custom
> > 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
Hy again;
Sorry, there was a typo in my example. Of course
it must be:
1.) From within the cocoon sitemap you would
create something like this within a pipeline:
regards, hussayn
SAXESS - Hussayn Dabbous wrote:
Hy;
I'm also new to cocoon, but i think, your
problem can be so
Hy;
I'm also new to cocoon, but i think, your
problem can be solved directly using the
sitemap capabilities by merging the two xml files with
aggregation then applying a stylesheet on the merged
data...
But you also could do it directly within the xslt context:
You can use the document() function
Hi Kasper,
You wouldn't need to write a custom transformer for this. One
solution would be to use aggregation to aggregate both files
together. Then using xsl you can extract the necessary data
for output.
Hope that helps.
Cheers,
Kasper,
I'm kinda new at this too, but I believe you can do that easily with
xslt...just define two components and stylesheets in your
pipeline...one to include the first xml file and one to include the
second one.
There may be a faster/easier way to do this ;-)
Bob Hitchins
-Original
13 matches
Mail list logo
