From: David Carlisle <davidc(_at_)nag(_dot_)co(_dot_)uk>
Reply-To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] Complex Condition problem with Attributes
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
...] / @...
not
...] @...
so
<xsl:when test="//*[contains(name(),'DebtManagement') and
(//*[contains(name(),'DebtManagement')]/@action='add' or
//*[contains(name(),'DebtManagement')]/@action='delete')">
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)
"//*[contains(name(),'DebtManagement')
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')[(_at_)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.
David
I think you missed off a ].
//*[contains(name(),'DebtManagement')][(_at_)action='add' or @action='delete']
Joe
--~------------------------------------------------------------------
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>
--~--