Bertrand LUPART wrote:

...

It *is* a bit odd, but it used to be the default behaviour, so it was made like that for compatibility reasons, iirc. These things are old... :)

One can expect that an RXML entity can output another RXML entity, which would then be parsed.

I'm not fond of RXML as a programming language, but out of curiosity, what is the expected behaviour?

The parser in Roxen for RXML usually evaluates one level deep, and doesn't reparse; in order for it to reparse, you need to <eval> the new part explicitly.