Michael Semcheski wrote:
I was wondering what kind of responses I would get to this question...
I have a template whose match looks kind of like this:
match="z:row[(_at_)Type='Matrix']/z:row[(_at_)MatrixOpt='1']
| z:row[(_at_)Type='Matrix']/z:row[(_at_)MatrixOpt='5']
| z:row[(_at_)Type='Matrix']/z:row[(_at_)MatrixOpt='6']"
(I added the line breaks to make it a little easier to read.) Basically,
this seems like a cumbersome way to write this rule. Any suggestions?
Move selection logic to caller - that's much more effective. I mean select
nodes to process by <xsl:apply-templates> and not by <xsl:template> if you
have such a convolute logic. I mean
<xsl:apply-templates
select="z:row[(_at_)Type='Matrix']/z:row[(_at_)MatrixOpt='1']
| z:row[(_at_)Type='Matrix']/z:row[(_at_)MatrixOpt='5']
| z:row[(_at_)Type='Matrix']/z:row[(_at_)MatrixOpt='6']"/>
...
<xsl:template match="z:row">
...
</xsl:template>
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list