There is nothing wrong with the templating approach, but if you are not familiar with them, you should glance at the many XML modules on CPAN as well.
You could either create the entire xml as needed, or have an xml template that you parse, then just change the values of whatever nodes needed. This may give you more flexibility in some cases.
Example using XML::Twig:
#!/usr/bin/perl
use strict;
use warnings;
use XML::Twig;
my $xml = do { local $/; <DATA>; };
my %data = (
name => 'Billy',
age => 12,
);
my $t = XML::Twig->new(
twig_handlers => {
name => sub { $_->set_text( $data{name} ); },
age => sub { $_->set_text( $data{age} ); },
},
pretty_print => 'indented',
);
$t->parse( $xml );
$t->flush;
__DATA__
<?xml version="1.0" ?>
<root>
<name>THIS CHANGES</name>
<static>blah blah blah</static>
<static>blah blah blah</static>
<age>THIS CHANGES</age>
</root>
-
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.
|