I managed to get it out badly with

my @nodes = $tree->findnodes('//tr');
for my $node (@nodes) {
@text = $node->findvalues('td') or next;
print Dumper \@text;
[download]

It is bad, in that I still have no clue what xpath is doing, despite reading documentation on it. It only works because as far as i can see, there is only one table... I am trying to get the following data parsed:

<ul><li>There was registered attempt to establish connection with the 
+remote host. The connection details are:</li></ul>
<p><table class="tbl" cellpadding="5" cellspacing="0">
<tr><td class="cell_1_h">Remote Host</td><td class="cell_2_h">Port Num
+ber</td></tr>
<tr><td class="cell_1">192.5.5.241<td class="cell_2">8091</td><tr>
</table></p>
[download]

but am having zero luck. I am trying:

my @nodes = $tree->findnodes('//ul');
for my $node ?(@nodes) {
my $text2 = $node->findvalue('li') or next;
if ($text2 =~ m/connection details are/) {
    print "$text2\n";
    my @text = $node->findvalues('/tr/td');
    print @Dumper \@text;
    }
}
[download]

The problem is, it clearly finds the li node, matches it, and then tries to run the findvalues against /tr/td. This totally doesn't work.... I have tried '/tr/td', '//tr/td', 'td', and cant get any of them to work at all. The total format of the section, as pasted from above is:

<ul><li>....connection...</li></ul>
<p><table>
<tr><td>stuff</td><td>stuff2</td></tr>
.
.
.
</table> </p>
[download]

What the heck is the xpath of the items below that section? Is it even possible to match this? I totally dont understand xpath at all....

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.