XOM API for Processing XML with Java

[Elliotte Harold <elharo AT metalab.unc.edu>]

Michael Kay wrote:
> > It shouldn't matter but you're not setting namesapce aware to true.
> >
> > Do you have a sample doc?
>
> One possibility is that there's a rogue JAR file or system property setting
> that's causing some SAX filter to be picked up instead of the real XML
> parser. User-written SAX filters often cause trouble because they tend to be
> less than 100% conformant to the SAX spec. Try establishing the class name
> of the actual XML parser that was loaded by the factory methods.

But XOM does not trust unknown SAX filters for exactly that reason. With 
a few known exceptions like Norm Walsh's catalog resolver. all data 
coming from filters is verified so empty string names shoudl cause a 
build error.

--
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/