Hi,
I'm new to this list, so first I'd just like to say how nice dom4j looks!
I've been trying to decide whether to use dom4j or JDOM on the
project that I'm working on, and just I keep comming back to dom4j for
it's clean and flexible design.
The one thing that I really liked was the so-called "pruning mode", which
allows processing only elements that I'm interested in. I do have a
question about this though...
It appears that for any single parse, you can only specify a single path
for which you'd like to prune elements. What would be nice, is if you
could specify a set of paths to prune and associate each path with a
different ElementHandler implementation. I've been able to do this, but
with more hacking than I really wanted to. Let me explain...
In looking at the org.dom4j.io.SAXReader and org.dom4j.io.SAXContentHandler
classes it seemed that all I may need to do was extend the SAXReader class
and override the createContentHandler method to create a SAXContentHandler
which used my own custom ElementStack subclass. I couldn't do this though,
as
the ElementStack class isn't public, so I can't extend it's functionality.
Would it
be possible to make this class public, to allow application level
derivations? Is
there any reason not to do so? Does this make sense or am I missing
something
obvious?
Thanks,
Dave White
--
_______________________________________________
dom4j-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dom4j-dev
