This XSL transformation has been taking very long and after trying to minimize
all the other inefficiencies, I'm left with the following code that I don't
know how to minimize.
<xsl:if test="Category != ''">
<TD NOWRAP="NOWRAP" VALIGN="TOP" ALIGN="LEFT">Cat:
The XML is of the following format
<?xml version="1.0" encoding="UTF-8"?>
100s of vform elements
Let me know if you'd like the full XSL code.
Any ideas why it is taking so long (using Xalan) and can this output be
achieved by other means?
I appreciate your help!
Ashish D. Tengshe
IT System Analyst
Principal Financial Group
From: John-Patrick Stacey
Of J-P S
Sent: Thursday, August 26, 2004 1:52 PM
Subject: Re: [xsl] XSL and infinite loops
On Thu, 26 Aug 2004, David Carlisle wrote:
) so if you are trying to avoid DOS attacks you could try to restrict the
) select attribute so it only uses Xpaths that select descendent children
Is there a danger list for such attacks? Presumably things like the
attributes on xsl:output etc. are right out; and anything in the
additional namespace of something like saxon: would be considered suspect.
Would it be possible to construct a SafeXSL stylesheet, that transforms
any dangerous XSL out? My first instinct is yes, because XSL is
functional, but that's only an instinct.
Just one small point for those Warwick supporters who've weighed in with the
argument that "We use microchips to find lost pets, so why not missing
children?". Chips in animals aren't tracking devices, they're used - because
pets can't talk - to establish who their owners are once the animals have been
found. Or for identifying their bodies.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>