[XOM-interest] Exposing XMLHandler
Elliotte Harold
elharo at metalab.unc.edu
Fri Sep 28 19:03:00 EDT 2007
Alan Gutierrez wrote:
>
> Please reread the message that I sent yesterday. I put a good deal of
> time into it. In it you will find the use case, a very common use case,
> that calls for an independent and public ContentHandler and
> LexicalHandler implementation that builds an XOM document. You will find
> a link to examples of the independent and public ContentHandler and
> LexicalHandler implementations that generate W3C DOM, Saxon TinyTree,
> and DOM4J.
>
I have read it and looked at some of your references, but it will take
time. I can't give a quick answer. From what I've looked at so far, I'm
not convinced you actually need what you say you need. It may be enough
to use a custom XMLReader instead, which is what XOM is designed to do.
The question I ask is two fold:
1. What does exposing XOMHandler let you do?
2. Is there no other way to do that within the existing API?
One of the design principles of XOM is that there's only one way to do
it. :-)
--
Elliotte Rusty Harold elharo at metalab.unc.edu
Java I/O 2nd Edition Just Published!
http://www.cafeaulait.org/books/javaio2/
http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/
More information about the XOM-interest
mailing list