XOM API for Processing XML with Java

[Peter Murray-Rust <pm286 AT cam.ac.uk>]

Thanks for your efforts, Elliotte,
I agree there is no way of reproducing the bug. For me Xerces seems like a
virus where every copying operation introduced small mutations so every
version is subtly different. But we have to rely on it.

P.


On Thu, Sep 24, 2009 at 11:50 AM, Elliotte Rusty Harold
<elharo AT ibiblio.org>wrote:

> After a great deal of effort, I have not been able to reproduce this
> bug at all. I've made a few adjustments that may cure the problem, but
> I have no way of knowing for sure.  I did find one way in which a
> misbehaving parser could sneak bad data into XOM and plugged that gap.
> However as to this specific bug I just don't see any way it could
> possibly have arisen if the reporters were in fact using any version
> of Xerces. :-(
>
> --
> Elliotte Rusty Harold
> elharo AT ibiblio.org
> _______________________________________________
> XOM-interest mailing list
> XOM-interest AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/xom-interest
>



-- 
Peter Murray-Rust
Reader in Molecular Informatics
Unilever Centre, Dep. Of Chemistry
University of Cambridge
CB2 1EW, UK
+44-1223-763069