Subject: [xsl] Data-driven XSLT code using dynamic mode values? From: "Costello, Roger L." <costello@xxxxxxxxx> Date: Fri, 2 Aug 2013 14:26:40 +0000 |
Hi Folks, I want to have multiple templates for the same element, each template processes the element differently. "Use modes," you say. Okay, sounds good. So I will have multiple template rules: <xsl:template match="Header" mode="Remove"> <xsl:template match="Header" mode="Replace"> <xsl:template match="Header" mode="Reject"> Now let's turn to the problem of firing the appropriate template rule. I have a variable which has a value that indicates whether I should do a Remove, Replace, or Reject: <xsl:variable name="action" select="get the action from an XML file" /> I want to fire a template rule based on the value of $action. Here's what I really, really want to do: <xsl:apply-templates select="." mode="$action" /> That would be so cool. That would truly be "data-driven code." Unfortunately, using a variable as the value of @mode is not allowed. Bummer. Is my only solution to use xsl:choose: <xsl:choose> <xsl:when test="$action eq 'Remove'"> <xsl:apply-templates select="." mode="Remove" /> </xsl:when> <xsl:when test="$action eq 'Replace'"> <xsl:apply-templates select="." mode="Replace" /> </xsl:when> <xsl:when test="$action eq 'Reject'"> <xsl:apply-templates select="." mode="Reject" /> </xsl:when> </xsl:choose> That is an awful solution. It is brittle and not extensible code. Please, please show me a better way than using xsl:choose. /Roger
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] [ANN] Release of Xmplify 1.3., Damian Morris | Thread | Re: [xsl] Data-driven XSLT code usi, Hermann Stamm-Wilbra |
[xsl] [ANN] Release of Xmplify 1.3., Damian Morris | Date | Re: [xsl] Data-driven XSLT code usi, Hermann Stamm-Wilbra |
Month |