XOM API for Processing XML with Java

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

I'll have to look at this when I get home. My guess is it's a bug in the 
Catalog resolver. What happened between 1.1a2 and a3 is that previously 
XOM trusted the catalog resolver not to introduce well-formedness 
errors. However after I discovered some problems (involving namespaces) 
where the catalog resolver did exactly that I stopped trusting it. Thus 
I suspect the bug existed in a2. XOM just didn't catch it. Now it does.

Anyway, I'll look into it.

--
Elliotte