[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: xslt 1.0 vs xslt 2.0 problem

Subject: Re: xslt 1.0 vs xslt 2.0 problem
From: "Darcy Parker" <darcyparker@xxxxxxxxx>
Date: Wed, 3 Sep 2008 13:41:08 -0400
Re:  xslt 1.0 vs xslt 2.0 problem
Hi Mark,

//A[ contains(B/@a, "foo") ]

is going to return just A nodes that have B/@a with "foo" in it... so
it should actually return

<resp>
  <A>
   <B a="foo bar bar"></B>
   <B a="bar bar foo"></B>
   <B a="boo far far"></B>
  </A>
  <A>
   <B a="far boo"></B>
   <B a="foo bar foo"></B>
   <B a="bar foo bar"></B>
  </A>
 </resp>

Because each of the A elements contain a B/@a with "foo" in it.

If you just want
<resp>
  <A>
   <B a="foo bar bar"></B>
   <B a="bar bar foo"></B>
  </A>
  <A>
   <B a="foo bar foo"></B>
   <B a="bar foo bar"></B>
  </A>
 </resp>

Others correctly suggested  //A[B[contains(@a, "foo")]]

But this will still just select the same 2 AA elements with the B
elements unchanged.

I think you want to do something like:

<xsl:for-each select=" //A[B[contains(@a, "foo")]]">
   <A>
      <xsl:apply-templates select="B[contains(@a, "foo")]"/>
  </A>
</xsl:for-each>

This way you are selecting each of the desired A elements... and
filtering out the B elements that do not have the correct @a values.

Darcy
On Wed, Sep 3, 2008 at 1:27 PM, mark bordelon <markcbordelon@xxxxxxxxx> wrote:
> Dear Gents:
>
> I have looked everywhere for the solution to this problem and never seem to get what to the root of the issue. Here is the problem in a nutshell:
>
> I have XML of this structure:
>
> <resp>
>  <A>
>   <B a="foo bar bar"></B>
>   <B a="bar bar foo"></B>
>   <B a="boo far far"></B>
>  </A>
>  <A>
>   <B a="far boo"></B>
>   <B a="foo bar foo"></B>
>   <B a="bar foo bar"></B>
>  </A>
> </resp>
>
> Using XSLT 1.0 (which I must, since I am constrained to use ASP.NET 2.0) I need to query the XML above to find all <A> if any of its children <B> fulfill a certain requirement.
>
> //A[ contains(B/@a, "foo") ]
>
> What I am seeing is that this XSL only checks the FIRST child node's (B) attribute instead of checking all of them. In other words, I only get this:
> <resp>
>  <A>
>  <B a="foo bar bar"></B>
>  </A>
> </resp>
> ...instead of what I need, namely this:
> <resp>
>  <A>
>  <B a="foo bar bar"></B>
>  <B a="bar bar foo"></B>
>  </A>
>  <A>
>  <B a="foo bar foo"></B>
>  <B a="bar foo bar"></B>
>  </A>
> </resp>
>
> An attempt to alleviate this problem by amalgamating all the <B> together using string-join, i.e.
>
> //A[ contains( string-join(B/@a), "foo") ]
>
> error-out because string-join is XSLT 2.0
>
> So...what is the correct way to query through all child nodes using xslt 1.0?
>
> Thanks Guys!
>
> Sincerely,
> Mark Bordelon
> Getty Trust

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.