Hi ,

Probably something really simple, but I'm stuck.

This is a stylesheet for calculating a breadcrumb trail in an external XML file.

The main template calls a template named "findbreadcrumb" that goes to work on the external file.

It works great, but:
once I want to output the Result, which is the variable $breadc, it comes up empty.

When I output the result IN the actual breadcrumb routine, it's there and correct: this is at the spot


Could anybody give me a hint why that correct variable is gone after I've left the template ?

The node for which I am calculating the breadcrumb is nr. 75 which is there and not empty.

Again: I've triple checked the routine and it works fine.
I'm just losing the variable...

Cheers and thanks in advance

Matthieu Brandt
email:[email protected]

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
     version="1.0">

    <xsl:variable name="varbreadc">
    </xsl:variable>
    <xsl:variable name="breadc">
    </xsl:variable>

    <xsl:variable name ="varmenuid" select="75">
    </xsl:variable>


    <xsl:template match="/">

         <xsl:call-template name="findbreadcrumb">
             <xsl:with-param name="menuid" select="$varmenuid"/>
             <xsl:with-param name="breadc" select="$varbreadc"/>
         </xsl:call-template>


         Result: <xsl:value-of select="$breadc" />



    </xsl:template>


     <xsl:template name="findbreadcrumb">
         <xsl:param name="menuid"/>
         <xsl:param name="breadc"/>

         <xsl:for-each select ="document('h:\XML\MenusWithPageCount.xml')/datarootmenu/MenusWithPageCount/Main_menu_nr[. = $menuid]">

                 <xsl:call-template name="bc">
                         <xsl:with-param name="breadc" select="parent::node()/Main_menu_name" />
                         <xsl:with-param name="parentnr" select ="parent::node()/Parent_menu_nr"/>
                 </xsl:call-template>

         </xsl:for-each>

     </xsl:template>

     <xsl:template name="bc">
           <xsl:param name="breadc" />
           <xsl:param name="parentnr"/>

           <xsl:choose>
                  <xsl:when test="$parentnr &gt; '0'">
                        <xsl:for-each select ="//MenusWithPageCount">
                          <xsl:if test ="Main_menu_nr = $parentnr" >
                                <xsl:call-template name="bc">
                              <xsl:with-param name="breadc" select= "concat (Main_menu_name,'---',$breadc)"/>
                             <xsl:with-param name="parentnr" select = "Parent_menu_nr"/>
                             </xsl:call-template>
                     </xsl:if>
                 </xsl:for-each>
           </xsl:when>

         <xsl:when test="$parentnr = '0'">
             <!-- Finished with breadcrumb routine
                             Variable $breadc is correctly filled-->
              </xsl:when>
          </xsl:choose>

     </xsl:template>

 </xsl:stylesheet>

Your variable is out of scope within the main template. There are a number of other points, the main being you would be much better off having the external document in a variable such as:
Then you pass the name of the file, for testing it will assume the default, change the for-each to:
Why access the menu data like this, why not just pass the file to the processsor?



--

Joe (Co-author Beginning XML, 3rd edition)

P.S. Looks like your xml file has a different structure to before so show a small sample if you need more help.

Hi Joe

And thanks for your reply. I knew it was something with scopes....
But I'm still unsure how to repair it.

I will definitely study your remarks on the other points.
The reason I pass the file as an external document, is that I'm trying to figure out a way to work with two (or more XML) files.

The output is going to be one html page that has a bunch of stuff on it. This is the main XML file that the processor needs to handle.

That page will also need some other info from other XML files.
The breadcrumb being the most complicated one (for me).

Because the main xsl file will be big, I'm trying to program everything in neat little blocks and just import de xsl files seperately, have them work on any XML files they need.
But I'll need to pass some variables to those XSL templates and get some others back.

The xml file was indeed changed a bit:
this is what it looks like now :

<datarootmenu>
<MenusWithPageCount>
<Main_menu_nr>1</Main_menu_nr>
<Main_menu_name>Principles and Tricks</Main_menu_name>
<Parent_menu_nr>0</Parent_menu_nr>
<Sort_parent_menu_nr>1</Sort_parent_menu_nr>
<CountOfPage_nr>0</CountOfPage_nr>
</MenusWithPageCount>

..
..
..

<MenusWithPageCount>
<Main_menu_nr>74</Main_menu_nr>
<Main_menu_name>Inversions on D</Main_menu_name>
<Parent_menu_nr>63</Parent_menu_nr>
<Sort_parent_menu_nr>2</Sort_parent_menu_nr>
<Page_id>170</Page_id>
<CountOfPage_nr>2</CountOfPage_nr>
</MenusWithPageCount>

<MenusWithPageCount>
<Main_menu_nr>75</Main_menu_nr>
<Main_menu_name>Bass walk down</Main_menu_name>
<Parent_menu_nr>4</Parent_menu_nr>
<Sort_parent_menu_nr>1</Sort_parent_menu_nr>
<Page_id>0</Page_id>
<CountOfPage_nr>0</CountOfPage_nr>
</MenusWithPageCount>

</datarootmenu>

I guess I'm not used to working with 'scopes' etc.
And I used to be a computer programmer for a living (back in the 80's)
. Even worked on one of the parent::node() of internet.
XML and XSLT are exciting and just what the doctor ordered for the stuff I'm doing now: I'm writing a web based music book, throwing it into a database and then (hopefully) retrieving it in multiple formats.

Anyway: just like to tell you that I appreciate the help very much!

Cheers from the Netherlands,

Matthieu Brandt