Re: [xsl] Complex Condition problem with Attributes

Subject: Re: [xsl] Complex Condition problem with Attributes
From: David Carlisle <davidc@xxxxxxxxx>
Date: Thu, 15 Sep 2005 13:32:06 +0100
> It failes at the position @.  But why?

you can't just put an axis (or an abreviated  axis such as @) straight
after a predicate: you have to separate steps in an XPath expression
with / so its
...] / @...
...]  @...

<xsl:when test="//*[contains(name(),'DebtManagement') and
(//*[contains(name(),'DebtManagement')]/@action='add' or

is legal but doesn't test what you want to test.

(do you really want to use // it's very expensive operation: searching
the whole document to arbitrary depth)

finds the elements you want but then (I think) you want to know if
_those_ elements have an add or delete action, but your test just
searches the entire document again (twice) finding the same eleemnts
each time.

I think you want

//*[contains(name(),'DebtManagement')[@action='add' or @action='delete']

But if you can use something other than // it is likely to be more
efficient. Or you could use a key.


This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:

Current Thread