After Josh's good analysis and solution for your problem I want to add
some comments from the XSLT point of view. The solution is
"sub-optimal", you have to bad axes in your expression: the descendant
axis ('//') and the preceding axis. Both used in combination can slow
down the processing extr
his helps,
Josh
-Original Message-
From: Michael Gerzabek [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 2:59 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: XSL question (was: XSL question in Cocoon)
Indeed that would be the right place, thanks.
Any
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 2:59 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: XSL question (was: XSL question in Cocoon)
Indeed that would be the right place, thanks.
Anyway since I use Cocoon with Xalan as XSLT Processor I'm not
su
Indeed that would be the right place, thanks.
Anyway since I use Cocoon with Xalan as XSLT Processor I'm not
sure where the problem belongs to. So I'll have a second run now
with results enclosed.
I've an input xml [1] that gets transformed with an xsl [2] and I think
the result should look like
