Altova Mailing List Archives


Re: [xsl] getting the node position in source xml in a variable

From: Jeni Tennison <jeni@---------------->
To:
Date: 2/27/2002 4:17:00 AM
Hi Gurvinder,

> That excatly is the problem...
> all the nodes in the $displaynodes are not siblings...

Ahh...

> coz i have something like this
> <test>
>   <nodes>
>         <level2>
>                 <data>3</data>
>                 <display>C</display>
>                 <someotherdata>abc</someotherdata>
>         </level2>
>         <level2>
>                 <data>2</data>
>                 <display>B</display>
>                 <someotherdata>abc</someotherdata>
>         </level2>
>         <level2>
>                 <data>1</data>
>                 <display>A</display>
>                 <someotherdata>abc</someotherdata>
>         </level2>
>   </nodes>
>  </test>

If the data and display elements that you want to associate are
already associated (as they are in this structure) then why not just
use that association?

For example, rather than using the lookup template at all, you could
just do:

  <select name="test">
    <xsl:for-each select="/test/nodes/level2">
      <xsl:sort select="display" />
      <option id="{data}" value="{data}">
        <xsl:value-of select="concat(data, '-', display)" />
      </option>
    </xsl:for-each>
  </select>

I guess that you're using the lookup template so that you can create
other select elements in the same kind of way elsewhere. Making the
lookup template absolutely generic will make it comparatively
inefficient, so before going to that extreme, perhaps you could
describe the variety of situations in which you want to use the lookup
template? For example, are the display nodes and associated data nodes
always siblings of each other, nested under some other node?

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.