[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
I've done this in the past by merging the two XML documents - basically inserting the specification (your attributes node) into the XML document to be processed as a child of the documentElement (that can be readily identified by name), then using XPaths to get at the variables. Post-transform, strip out the spec node (if you need to preserve or further process the XML document). Don't know the syntax for Xalan-J - but I'm assuming there's something equivilent to appendChild() and removeChild().
~Duane
----- Original Message ----- From: "Martin Heiden" <martin.heiden@xxxxxxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Saturday, April 28, 2007 10:44 AM
Subject: [xsl] Evaluating condition strings
Re: [xsl] Evaluating condition strings
Subject: Re: [xsl] Evaluating condition strings From: "Duane Hitz" <dhitz@xxxxxxxxxxxxxxxx> Date: Sat, 28 Apr 2007 14:55:18 -0600 |
I've done this in the past by merging the two XML documents - basically inserting the specification (your attributes node) into the XML document to be processed as a child of the documentElement (that can be readily identified by name), then using XPaths to get at the variables. Post-transform, strip out the spec node (if you need to preserve or further process the XML document). Don't know the syntax for Xalan-J - but I'm assuming there's something equivilent to appendChild() and removeChild().
~Duane
----- Original Message ----- From: "Martin Heiden" <martin.heiden@xxxxxxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Saturday, April 28, 2007 10:44 AM
Subject: [xsl] Evaluating condition strings
Hi!
I've got a XML doc which contains a description of a final document. This XML doc uses tags that handle conditions:
<if condition="var1 = true or var2 < 5 and var3 = 'ok'"> <then> text </then> <else> another text </else> </if>
the variables are available in another XML doc: <attributes> <variable name="var1">false</variable> <variable name="var2">4</variable> <variable name="var3">ok</variable> </attributes>
I think I could evaluate the conditions by writing an extension for the xslt processor (I'm using Xalan-J) or parsing the conditions before the transformation process (maybe with a dynamic language like groovy because the variables are not typed.).
Could it be done with pure XSLT? What approach would you recommend?
TIA
Martin
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re[2]: [xsl] Evaluating condition s, Martin Heiden | Thread | [xsl] fo:static-content, Mati Hadi |
Re: [xsl] Evaluating condition stri, David Carlisle | Date | Re: [xsl] Xoath quote escaping, Duane Hitz |
Month |