[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

AW: [xsl] problem with intersect in match pattern

---

---

Great !
Thank you guys !



. . . . . . . . . . . . . . . . . . . . . . . . . .
Ing. Patrick Szabo
Developer
LexisNexis
A-1030 Wien, Marxergasse 25

mailto:Patrick.Szabo@xxxxxxxxxxxxx
Tel.: +43 1 53452 1514
Fax.: +43 1 534 52 146

. . . . . . . . . . . . . . . . . . . . . . . . . .

-----Urspr|ngliche Nachricht-----
Von: Abel Braaksma (Exselt) [mailto:abel@xxxxxxxxxx]
Gesendet: Freitag, 06. Juni 2014 13:35
An: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Betreff: Re: [xsl] problem with intersect in match pattern


On 6-6-2014 12:44, Martin Honnen martin.honnen@xxxxxx wrote:
> Szabo, Patrick (LNG-VIE) patrick.szabo@xxxxxxxxxxxxx wrote:
>
>> <snip />
>
> I think you want
>   <xsl:variable name="var1" select="//desiredelement"/> to select the
> original elements and not to create a copy of element as you currently
> do.
>
>> <snip />
>
> Then the intersection should work.

The underlying reason that intersect didn't work in the previous example is
that it uses node-identity, as opposed to content-equality (as with
fn:deep-equal). Creating a copy of a node changes its node-identity and
"disconnects" it from the underlying document (an input document is immutable
just as variables are immutable).

Cheers,

Abel Braaksma
Exselt XSLT 3.0 streaming processor
http://exselt.net

---