Quote:
quote:Originally posted by samjudson
I think you mean name() rather than node().
And generally if you want things removed in XSLT you usually try to apply templates to everything else, and then have a blank template for the ones you want to ignore (rather than specifically applying a template to the ones you don't want to do anything with, which seems counter-productive).
/- Sam Judson : Wrox Technical Editor -/
|
I've tried name() before as well. No change.
The rest of what you say is obvious to me. What I'm looking for is a looping algorithm that goes through the xml file, looking for anything with the word 'Queue' as the name of the node. <Queue1> or <Queue2>. I can try to ignore those fields by applying templates to everything else, but without specifying each and every <QueueX> tag, the templates I set up usually remove the other sibling tags that I do not want removed.
Everything I have seen so far, starts-with or contains (or pretty much everything I have seen in tutorials and books), only has string functions that apply to the element of the node or the attributes. But not for the name of the node specifically...unless it's trying to match or select it. Such as, I would like to have...
<xsl:template match="ErrorLog/Error/Queue*">
where the * is for anything that has Queue for the first 5 characters. However, it is becoming apparent that xslt does not allow for this kind of wildcard functionality.