OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Choosing the correct XML API

[ Lists Home | Date Index | Thread Index ]

At 3:02 PM -0700 6/29/04, Landon Blake wrote:

I would like to work with an XML API that allows me to search an XML 
document for elements according to the name of the element, attribute 
of the element, or the value of a child element. Once a matching 
element was found it would be written to another XML file or 
converted to a Java object for use by my program. I do not want to 
have to read the entire document into memory, like you are required 
to with JDOM. (The idea is to read/parse a large XML document, and 
only pull out what you need.) Can anyone reccomend an XML API that 
would meet these needs, or should I be trying to implement this on my 
own by adding a layer on top of SAX itself? (I program in Java.)

Probably the easiest way to do this given the restriction not to load 
the entire document into memory is is by subclassing the NodeFactory 
class in XOM. http://www.cafeconleche.org/XOM/ Without the memory 
restriction I'd be looking at XPath.

   Elliotte Rusty Harold
   Effective XML (Addison-Wesley, 2003)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS