Subject: RE: [xsl] Which one's faster From: "Michael Kay" <mhk@xxxxxxxxx> Date: Wed, 2 Jul 2003 15:36:47 +0100 |
> It is not a choice to be made. Example 1 does not work > because xsl:attribute is designed to exactly what you are > intending. In particular, you can not place an xpath query > (i.e. @url) in the output directly. I imagine the example was intended to read href="{@url}" which is of course perfectly OK. Michael Kay The XSLT processor does > not know that is should be interpreted as an xpath query. The > same query in the select attribute of the xsl tag is > interpreted as an xpath query and thus works. > > - Angus > > -----Original Message----- > From: Carlos Barroso [mailto:est-c-barroso@xxxxxxxxxxxxx] > Sent: Wednesday, July 02, 2003 5:31 AM > To: xsl-list-digest@xxxxxxxxxxxxxxxxxxxxxx > Subject: [xsl] Which one's faster > > Hy there. > I would lie to know which version is faster for the transformer: > > Example 1: > > <xsl:template match="/"> > <xsl:for-each select="SITE" /> > <p><a href="@url"></a></p> > </xsl_for-each> > </xsl:template> > > > Example 2: > > <xsl:template match="/"> > <xsl:for-each select="SITE" /> > <p> > <a> > <xsl:attribute name="href"> > <xsl:value-of select="@url" /> > </xsl:attribute> > </a> > </p> > </xsl_for-each> > </xsl:template> > > In resume, what's faster: creating the text directly or using > the <xsl:attribute> for generating the text? > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Which one's faster, Jeni Tennison | Thread | RE: [xsl] msxml xpath problem, Jim Fuller |
RE: [xsl] Parsing xsl:variable into, Michael Kay | Date | Re: [xsl] Dynamic Sort Value Solved, David Carlisle |
Month |