You need to change your tree from
my $tree = {
arr => {
elem => [
{
mod => 'mstring1',
rp => 'rstring1',
subarr => {
subelem => [
{content=>'...'}, {content=>'...'},
]
}
},
{
mod => 'mstring2',
rp => 'rstring2',
subarr => {
subelem => [
{content=>'...'}, {content=>'...'},
]
}
},
],
}
};
to
my $tree = {
arr => {
elem => [
{
mod => { content => 'mstring1' }, <------
rp => 'rstring1',
subarr => {
subelem => [
{content=>'...'}, {content=>'...'},
]
}
},
{
mod => { content => 'mstring2' }, <------
rp => 'rstring2',
subarr => {
subelem => [
{content=>'...'}, {content=>'...'},
]
}
},
],
}
};
This can be done programmatically.
You can use ContentKey => ... to specify a name other than "content". I have used _text.
If you're creating the tree using XMLin, use ForceContent => 1. Here's a round-trip example:
use strict;
use warnings;
use Data::Dumper qw( Dumper );
use XML::Simple qw( );
local $XML::Simple::PREFERRED_PARSER = 'XML::Parser';
my $xs = XML::Simple->new(
ForceArray => [qw( elem subelem )],
ForceContent => 1,
#ContentKey => '_text',
KeyAttr => {},
KeepRoot => 1,
);
my $tree = $xs->XMLin(<<'__EOI__');
<arr>
<elem rp="rstring1">
<mod>mstring1</mod>
<subarr>
<subelem>...</subelem>
<subelem>...</subelem>
</subarr>
</elem>
<elem rp="rstring2">
<mod>mstring2</mod>
<subarr>
<subelem>...</subelem>
<subelem>...</subelem>
</subarr>
</elem>
</arr>
__EOI__
{
local $Data::Dumper::Indent = 1;
print(Dumper($tree));
}
print $xs->XMLout($tree);
Update: I had originally phrased the reply as if the OP started from XML. Rearranged contents.
Update: Added instructions on how to transform the tree programmatically.
-
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.