XOM API for Processing XML with Java

[Jacky Lu <Jacky.Lu AT Sun.COM>]

Elliotte Rusty Harold wrote:

> >Elliotte Rusty Harold wrote:
> >
> >>  >Hello, all,
> >>  >
> >>  >I'm wondering if XOM keeps the whole tree in the memory while parsing a
> >>  >large xml file(like what JDOM does).
> >>
> >>  That's the default. However, you have the option to provide a
> >>  NodeFactory subclass that does not do this, and instead process one
> >>  element at a time. XOM can process documents much larger than
> >>  available memory. There are examples of this in the samples package.
> >>
> >>  --
> >>
> >>     Elliotte Rusty Harold
> >>     elharo AT metalab.unc.edu
> >>     Effective XML (Addison-Wesley, 2003)
> >>     http://www.cafeconleche.org/books/effectivexml
> >>
> >>http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA
> >
> >So, in this way(subclassing NodeFactory), XOM functions like SAX, and thus 
> >not
> >comfortable in OO design, am I right? Thanks.
> >
>
> I do not know what you mean by "not comfortable in OO design"
> --
>
>    Elliotte Rusty Harold
>    elharo AT metalab.unc.edu
>    Effective XML (Addison-Wesley, 2003)
>    http://www.cafeconleche.org/books/effectivexml
>    
> http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA

Sorry, forgot my previous question, I got  your idea. With XOM,  We can 
create an
element in memory, and remove it from memory after processing it.  Of course 
the
element could be processed in any way we like.

Great XOM!  Thank you Elliotte.

Jacky