Assuming you do nothing but parse the document, the ranking of the different parser standards is as follows: 1. StAX is the fastest The event is reported to you 2. SAX is next It does everything StAX does plus the content is realized automatically (element name, namespace, attributes, …) 3. DOM is last It does … Read more
You could work with a generated XML parser using ANTLR4. The Following works very well on a ~17GB Wikipedia dump /20170501/dewiki-20170501-pages-articles-multistream.xml.bz2 but I had to increase heap size using -xX6GB. 1. Get XML Grammar cd /tmp git clone https://github.com/antlr/grammars-v4 2. Generate Parser cd /tmp/grammars-v4/xml/ mvn clean install 3. Copy Generated Java files to your Project … Read more
There is com.sun.xml.txw2.output.IndentingXMLStreamWriter XMLOutputFactory xmlof = XMLOutputFactory.newInstance(); XMLStreamWriter writer = new IndentingXMLStreamWriter(xmlof.createXMLStreamWriter(out));
The STaX API has support for the notion of not replacing character entity references, by way of the IS_REPLACING_ENTITY_REFERENCES property: Requires the parser to replace internal entity references with their replacement text and report them as characters This can be set into an XmlInputFactory, which is then in turn used to construct an XmlEventReader or … Read more
“Going back” in a stream implies some kind of memory, so there is no point in sticking to the most memory-efficient tool. XMLEventReader can handle this with ease: public class Main { public static void main(String args[]) throws Exception { Unmarshaller aUnmarshaller = JAXBContext.newInstance(A.class).createUnmarshaller(); Unmarshaller bUnmarshaller = JAXBContext.newInstance(B.class).createUnmarshaller(); Unmarshaller cUnmarshaller = JAXBContext.newInstance(C.class).createUnmarshaller(); try (InputStream input … Read more