Subject: Re: [xsl] Are long XPath statements inherently bad? From: John <john-xsl-list@xxxxxxxx> Date: Thu, 28 Oct 2004 10:49:48 -0700 |
As far as logic is concerned if you can simplify your XML result set with XPath instead of sending the entire tree through a series of xsl conditional logic elements
instead of sending the entire tree through a series of xsl conditional logic elements your probably better off. Of course without seeing your XML and what you ultimately want as output its tough to say one way or the other if there is a simpler way to accomplish this.
I am kind of wondering what this is:
[( @yearspecific, . ) != 1
Depending on the processor you are using you may be able to take advantage of the EXSLT date extensions.
With all of this said, you may very well be trying to create something that is much better served using a server side control with ASP.NET. If you are thinking of going this route anyway youre going to find yourself being much more productive using the calendar control that comes as part of the standard ASP.NET component library.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Are long XPath statements, Jeni Tennison | Thread | [xsl] output .net register directiv, Jan Limpens |
Re: [xsl] Performance degraded with, Kevin Jones | Date | Re: [xsl] Are long XPath statements, Jeni Tennison |
Month |