ansaurus

Question

Answer 1

A:

I figured it out.

I need to change my test to

<xsl:when test="contains($MainDeliveryCode, $CurrentDeliveryCode" >

That solved the problem.

http://www.zvon.org/xxl/XSLTreference/Output/function_contains.html is the documentation for the function.

Jeremy 2010-01-20 19:48:42

My recommendation would be to abandon your current XSLT and start over. ;) It might work, but the approach you take way to complicated and if it does not hurt you now, it will hurt you later.

Tomalak 2010-01-21 15:54:09

Already did it after you showed me how to do it with selecting instead of recursion. I have even tested the new code with no loops and no recursion and it works perfectly.

Jeremy 2010-01-21 16:32:06

Answer 2

+1 A:

There are a few things wrong with your implementation. Most important, the expression:

<xsl:variable name="CurrentDeliveryCode" select="$Lines/DLVYLOCCD"/>

returns a node-set consisting of all the DLVYLOCCD elements, not just the current one as you seem to assume. Also, you shouldn't be using recursion to iterate. Use instead, in which case you will process the items one at a time.

Jim Garrison 2010-01-20 22:19:34

+1 for "you shouldn't be using recursion to iterate".

Tomalak 2010-01-21 10:56:08

I used recusrion in this case because I need stop on the first match. The goal is to find the first address for a location print it and stop processing so that I don't print it more than once.What expression would return just the current one?

Jeremy 2010-01-21 14:36:06

Answer 3

+1 A:

Here is a less painful version of your XSLT:

<xsl:stylesheet 
  version="1.0" 
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>
  <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>

  <xsl:template match="data">
    <html>
      <head>
        <title></title>
      </head>
      <body>
        <!-- this selects the matching LINE node(s), or nothing at all -->
        <xsl:apply-templates select="
          Lines/LINE[DLVYLOCCD = /data/header/DLVYLOCCD]
        " />
      </body>
    </html>
  </xsl:template>

  <xsl:template match="LINE">
    <p>
      <!-- for the sake of the example, just output a copy -->
      <xsl:copy-of select="." />
    </p>
  </xsl:template>

</xsl:stylesheet>

gives (formatted result):

<?xml version="1.0" encoding="utf-8"?>
<html>
  <head>
    <title></title>
  </head>
  <body>
    <p>
      <LINE><DLVYLOCCD>155OO</DLVYLOCCD></LINE>
    </p>
  </body>
</html>

Tomalak 2010-01-21 11:03:53

Thanks but I needed to stop on the first match. I should have specified.

Jeremy 2010-01-21 14:37:10

@Jeremy: Why would you want to output the three "fails" before the match, but not the three after it? Or do you *actually* want to output the match only?

Tomalak 2010-01-21 15:05:02

I actually want to output the match only. I was outputting the fails as a diagnostic until I could devise a way to stop at the correct one.

Jeremy 2010-01-21 15:20:18

You must try to stop thinking about XSLT in an iterative/imperative way. It is a declarative programming language - you should never iterate until you have what you are looking for, but simply *select* what you are looking for. I'll change my answer accordingly.

Tomalak 2010-01-21 15:31:50

Do you have a good reference for how to select that I could use in the future?

Jeremy 2010-01-21 15:44:24

You would need to learn XPath. There are plenty of web pages that provide tutorials, and XPath isn't *that* hard actually.

Tomalak 2010-01-21 15:51:16

For XSLT/XPATH 1.0 I found Evan Lenz's "XSLT 1.0 Pocket Reference" (O'Reilly) to be a really good, inexpensive tutorial. It did a good job of communicating the essentials of declarative vs imperative style.

Jim Garrison 2010-01-21 21:05:42

ansaurus

tags:

views:

answers:

String comparison in XSLT

related questions