Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things


by mirod (Canon)
on Sep 05, 2000 at 16:10 UTC ( [id://31109]=modulereview: print w/replies, xml ) Need Help??

Item Description: Implements W3C's Document Object Model

Review Synopsis: Good module but the standard interface is really ugly


XML::DOM is a Perl implementation of W3C's DOM Level 1.

It is one of the most widely used Perl XML modules. It is included in libxml-enno

XML::DOM adds some Perl specific features to the W3C recommendation.

Why use XML::DOM?

  • you want to follow the W3C recommendation
  • you want to use one of the most stable XML modules in Perl
  • you already know the DOM, or you want to be able to use the same API in Java and in Perl in the future you want to interface easily with XML data bases
  • you are seriously masochistic!

Why NOT use XML::DOM

  • you have to process huge documents
  • you need speed
  • the DOM API is ugly!

Related Modules

  • XML::XQL::DOM adds XQL support to XML::DOM.
  • XML::DOM::ValParser uses XML::Checker to validate doccuments at parse time.
  • XML::EasyOBJ is a module built on top of XML::DOM with a simpler and more perlish interface. This kind of module is an excellent idea: it gives you the ease of programming of the Perl way while preserving DOM compatibility,
  • XML::DOM::Twig: a little module I wrote (it's not yet on CPAN) to emulate some of XML::Twig functions with XML::DOM, making it easier (and safer) to use.

Personal notes

I don't like the DOM API at all! I think the model is clean but for some reason the interface is clunky and too verbose. It is extremely Java oriented, from the names of methods to the type of object they return.

That said XML::DOM is a robust module, widely used and well designed. Plus the DOM is generally well documented and some nice tutorials are available.

Warning: there are compatibility problems between various versions of XML::DOM and XML::Parser. The valid combinations are XML::Parser 2.30 + XML::DOM 1.33 and above or XML::Parser 2.30 + XML::DOM 1.29 (included in libxml-enno) or XML-Parser 2.27 (included in Activestate Perl on Windows) + XML::DOM 1.25 (the stand-alone version not included in libxml-enno).

Replies are listed 'Best First'.
by deprecated (Priest) on Feb 25, 2001 at 14:46 UTC
    Please see my fixes for this module's installation process here if youre having problems getting it to work.

    brother dep.

by Anonymous Monk on Oct 25, 2000 at 19:45 UTC
    The warning for using v. 2.27 of XML::Parser was very helpful. I had just developed a system using XML::DOM and was rolling it out with the latest versions, and nothing would work. I knew it probably had something to do with the change to using the external expat libs, but it was a lot of headache debugging. This tip saved be a lot of time today!
      By the way, I have updated XML::DOM to fix some bugs and to work with the lastest version of XML::Parser (2.30). You can download it from here. If you do, let me know if it works!
by mirod (Canon) on Aug 31, 2001 at 20:02 UTC

    I so much hate the DOM API, and I so much like the XML::Twig API ;--), that I have written a quick module to port some of the XML::Twig methods to XML::DOM.

    It is not on CPAN, as I am not sure if it is really a good idea (plus the implementation is kinda crappy at the moment, instead of sub-classing XML::DOM I just pollute its classes with my methods) but you can get it here.

    I think what I am most proud of with this module is the logo...

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: modulereview [id://31109]
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others imbibing at the Monastery: (3)
As of 2024-05-22 04:15 GMT
Find Nodes?
    Voting Booth?

    No recent polls found