xml::dom::valparser(3) [redhat man page]

XML::DOM::ValParser(3)					User Contributed Perl Documentation				    XML::DOM::ValParser(3)

NAME

       XML::DOM::ValParser - an XML::DOM::Parser that validates at parse time

SYNOPSIS

	use XML::DOM::ValParser;

	my %expat_options = (KeepCDATA => 1,
			     Handlers => [ Unparsed => &my_Unparsed_handler ]);
	my $parser = new XML::DOM::ValParser (%expat_options);

	eval {
	    local $XML::Checker::FAIL = &my_fail;
	    my $doc = $parser->parsefile ("fail.xml");
	    ... XML::DOM::Document was created sucessfully ...
	};
	if ($@) {
	    # Either XML::Parser (expat) threw an exception or my_fail() died.
	    ... your error handling code here ...
	    # Note that the XML::DOM::Document is automatically disposed off and
	    # will be garbage collected
	}

	# Throws an exception (with die) when an error is encountered, this
	# will stop the parsing process.
	# Don't die if a warning or info message is encountered, just print a message.
	sub my_fail {
	    my $code = shift;
	    die XML::Checker::error_string ($code, @_) if $code < 200;
	    XML::Checker::print_error ($code, @_);
	}

DESCRIPTION

       Use XML::DOM::ValParser wherever you would use XML::DOM::Parser and your XML will be checked using XML::Checker at parse time.

       See XML::DOM for details on XML::DOM::Parser options.  See XML::Checker for details on setting the fail handler (my_fail.)

       The following handlers are currently supported, just like XML::DOM::Parser: Init, Final, Char, Start, End, Default, Doctype, CdataStart,
       CdataEnd, XMLDecl, Entity, Notation, Proc, Default, Comment, Attlist, Element, Unparsed.

XML
::DOM::ValParser
       XML::DOM::ValParser extends from XML::Checker::Parser. It creates an XML::Checker object and routes all event handlers through the checker,
       before processing the events to create the XML::DOM::Document.

       Just like XML::Checker::Parser, the checker object can be retrieved with the getChecker() method and can be reused later on (provided that
       the DOCTYPE section of the XML::DOM::Document did not change in the mean time.)

       You can control which errors are fatal (and therefore should stop creation of the XML::DOM::Document) by filtering the appropriate error
       codes in the global $XML::Checker::FAIL handler (see "ERROR_HANDLING" in XML::Checker) and calling die or croak appropriately.

       Just like XML::Checker::Parser, XML::DOM::ValParser supports the SkipExternalDTD and SkipInsignifWS options. See XML::Checker::Parser for
       details.

AUTHOR

       Send bug reports, hints, tips, suggestions to Enno Derksen at <enno@att.com>.

SEE ALSO

       XML::DOM, XML::Checker ("SEE_ALSO" in XML::Checker)

perl v5.8.0							    2000-01-31						    XML::DOM::ValParser(3)

XML::DOM::Parser(3)					User Contributed Perl Documentation				       XML::DOM::Parser(3)

NAME

       XML::DOM::Parser - An XML::Parser that builds XML::DOM document structures

SYNOPSIS

	use XML::DOM;

	my $parser = new XML::DOM::Parser;
	my $doc = $parser->parsefile ("file.xml");
	$doc->dispose; # Avoid memory leaks - cleanup circular references

DESCRIPTION

       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
       Clark's 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 XML::DOM::Parser class.
       Note that the 'Style' property should not be used (it is set internally.)

       The XML::Parser NoExpand option is more or less supported, in that it will generate EntityReference objects whenever an entity reference is
       encountered in character data. I'm 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 KeepCDATA 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.

Using LWP to parse URLs
       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:

	use LWP::UserAgent;
	$LWP_USER_AGENT = LWP::UserAgent->new;
	$LWP_USER_AGENT->env_proxy;

       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:

	XML::DOM::Parser::set_LWP_UserAgent ($my_agent);

       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.

perl v5.16.3							    2002-07-31						       XML::DOM::Parser(3)