Taking this question about beautiful XSL but getting more specific, how should I refactor this XSL to take advantage of apply-templates and/or keys.
I tend to “over use” for-each elements to control the context of the source and I can imagine that apply-templates can help. Despite much Google-ing, I still don’t understand how to control context within the multiple templates.
In the below example, how can the repetitive XPath segments be reduced by refactoring?
<xsl:template match="/">
<xsl:element name="Body">
<xsl:element name="Person">
<xsl:if test="/source/dbSrc/srv/v[@name='name']/text()='false'">
<xsl:element name="PhoneNumber" />
<xsl:element name="Zip">
<xsl:value-of
select="/source/req[1]/personal-info/address-info/zip-code" />
</xsl:element>
</xsl:if>
<xsl:if test="/source/dbSrc/srv/v[@name='name']/text()='true'">
<xsl:element name="PhoneNumber" />
<xsl:element name="Zip">
<xsl:value-of select="/source/req[3]/personal-info/address-info/zip-code" />
</xsl:element>
</xsl:if>
</xsl:element>
</xsl:template>
One initial way of refactoring the given code would be the following:
Do note: The refactored code doesn’t contain any conditional xslt instructions.
Further refactoring can let us get rid of the last too templates, because in this case additional templates aren’t actually needed — the code only creates a single element and depends on a single condition:
Note: Here we assume that
/*/dbSrc/srv/v[@name='name']/text()can have only two possible values:'true'or'false'