XML::DOM::Parser extends XML::Parser
The XML::Parser module was written by Clark Cooper and
is built on top of XML::Parser::Expat,
which is a lower level interface to James Clarks expat library.
XML::DOM::Parser parses XML strings or files
and builds a data structure that conforms to the API of the Document Object
Model as described at <http://www.w3.org/TR/REC-DOM-Level-1>.
See the XML::Parser manpage for other additional properties of the
Note that the Style property should not be used (it is set internally.)
The XML::Parser <B>NoExpandB> option is more or less supported, in that it will
generate EntityReference objects whenever an entity reference is encountered
in character data. Im not sure how useful this is. Any comments are welcome.
As described in the synopsis, when you create an XML::DOM::Parser object,
the parse and parsefile methods create an XML::DOM::Document object
from the specified input. This Document object can then be examined, modified and
written back out to a file or converted to a string.
When using XML::DOM with XML::Parser version 2.19 and up, setting the
XML::DOM::Parser option <B>KeepCDATAB> to 1 will store CDATASections in
CDATASection nodes, instead of converting them to Text nodes.
Subsequent CDATASection nodes will be merged into one. Let me know if this
is a problem.
The parsefile() method now also supports URLs, e.g. http://www.erols.com/enno/xsa.xml.
It uses LWP to download the file and then calls parse() on the resulting string.
By default it will use a LWP::UserAgent that is created as follows:
$LWP_USER_AGENT = LWP::UserAgent->new;
Note that env_proxy reads proxy settings from environment variables, which is what I need to
do to get thru our firewall. If you want to use a different LWP::UserAgent, you can either set
it globally with:
or, you can specify it for a specific XML::DOM::Parser by passing it to the constructor:
my $parser = new XML::DOM::Parser (LWP_UserAgent => $my_agent);
Currently, LWP is used when the filename (passed to parsefile) starts with one of
the following URL schemes: http, https, ftp, wais, gopher, or file (followed by a colon.)
If I missed one, please let me know.
The LWP modules are part of libwww-perl which is available at CPAN.