I hate unnecessary attributes. I try to use them only when it refines the meaning of the value of the element. If you create your xml with element values, I think you will have an easier time getting to them. Like this:
<log>
<msg>
<error>
ID not found
</error>
<request>
myRequest
</request>
</msg>
</log>
But sometimes we just have to deal with the hand we are dealt. I found a way to get at your attribute values by registering two TwigHandlers. I'm sure
mirod has a much more elegent solution than this:
use strict;
use XML::Twig;
my $file = 'uncle.xml';
my $twig = new XML::Twig( TwigHandlers => {
'log/msg/error' => \&print_error,
'log/msg/request' => \&print_request,
});
$twig->parsefile($file) or die "can't parse $!\n";
sub print_error {
my ($t, $elt) = @_;
print "ERROR = " . $elt->att('name') . "\n";
}
sub print_request {
my ($t, $elt) = @_;
print "REQUEST = " . $elt->att('name') . "\n";
}
Get Strong Together!!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.