Oops, lost this in my inbox :-( On Thu, 12 Jan 2017 at 19:22 Frederik Ramm <frede...@remote.org> wrote:
<snip> > I've re-built osmosis with Xerces 2.11.0 and this doesn't change the > situation. > > Should I perhaps try and build a minimal "use Xerces to parse this XML > file" program, and if I can replicate the problem with that, file a bug > with Xerces? Or is the way in which Osmosis uses Xerces somehow special > so that a simple program like that would be very unlikely to trigger the > bug? > I think it'd be a great place to start and think it *should* trigger the bug. But I'm not sure what we'd do about it :-) Osmosis doesn't do anything special that I can think of. It just uses the standard Java mechanisms to invoke XML parsing. One possible thing to try would be to use the XML parser used in the "fast" XML processor. It uses XML stream parsing as opposed to SAX parsing (i.e. pull vs. push processing). Brett
_______________________________________________ osmosis-dev mailing list osmosis-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/osmosis-dev
