Re: [xsl] Document processing order

Subject: Re: [xsl] Document processing order
From: "Joseph L. Casale jcasale@xxxxxxxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 7 Jul 2017 16:35:20 -0000
From: Michael Kay mike@xxxxxxxxxxxx [mailto:xsl-list-
Sent: Friday, July 7, 2017 9:52 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Document processing order

> I don't really see the problem, but that probably means I haven't
> your explanation. Perhaps you could illustrate it with an example.

Hi Michael,
This relates to the sample I posted yesterday, given the following:

<?xml version="1.0" encoding="utf-8"?>
<Wix xmlns="";>
        <DirectoryRef Id="WEBSITEDIR">
            <Component Id="cmpCA929998DABB546D9DBF11366AF00C73" Guid="*">
                <File Id="fil621D71236777E77CBCD8796C747EFDFF" KeyPath="yes"
Source="$(var.MyVar)\Global.asax" />
            <Component Id="cmp431AD7A30B0DC39715871007A26AE68B" Guid="*">
                <File Id="fil24F96AF9459A0FF6768697EEBAAA4133" KeyPath="yes"
Source="$(var.MyVar)\load.aspx" />
        <ComponentGroup Id="WebsiteComponents">
            <ComponentRef Id="cmpCA929998DABB546D9DBF11366AF00C73" />
            <ComponentRef Id="cmp431AD7A30B0DC39715871007A26AE68B" />

I create a template that matches Component elements where the child
File element has a specific Source attribute. That's simple, but then I need
to process the ComponentRef elements and omit any whose Id matches a
Component that I now have deleted.

I thought I could simply do something like;

  <xsl:template match="wix:Component[wix:File[substring(@Source,
string-length(@Source) - 4) = '.abcd]]

and then generate an xpath query to select all ComponentRef elements whose
Id is orphaned which seems to work in my editor using xpath 2, but the
is applied using xpath 1.

Thanks a lot for the help,

Current Thread