Fellow monks,
I have a problem regarding XML::LibXML, another great API by Matts.

I have an xml document like this:

<?xml version="1.0" encoding="ISO-8859-1" ?> 
<!DOCTYPE page SYSTEM "entities.dtd"> 
 
<form> 
  <method>POST</method> 
  <action>/cgi/process.cgi</action
  <input> 
    <type>text</type> 
    <name>name1</name> 
    <required>0</required> 
    <value></value> 
    <comment>This field is not required.</comment> 
  </input>
  <input> 
    <type>text</type> 
    <name>name3</name> 
    <required>1</required> 
    <value></value>  
    <comment>Put three words here!</comment> 
    <test> 
      my @tmp = split(/\ /, shift()); 
      return 1 if ( $#tmp == 2 ); 
      return 0; 
    </test> 
  </input>
</form>
[download]

The XML above creates a web form through the use of XSLT. The little bit of perl-code is stuffed through ev'l into a closure and the value of the CGI::param("name3") is put into that routine. If 0 returns we show the form again, if 1 returns we continue.

To be nice and informatife, I'd like to tell the user he/she is a stupid user. But I also like to store into my DOM the values to user already submitted. And I want to add another branch to the <form> trunk, holding information on why they failed.

I've tried _a lot_ in adding childs, nodes, childnodes, textchilds, you name it, but I just can't seem to get it done propperly.

I now have a hack, where I do:

$string = $dom->toString;
$string =~ s/<\/form>//gim;
$string .= "<info><failure>blah</failure></info>\n</form>\n";
$dom = $parser->parse_string($string);
[download]

This cannot be the purpose of libXML, and it surely is pretty expensive....



Er formait hyarya.
"Field experience is something you don't get until just after you need it."

---

---

• 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.