More specifically, the bug/problem is as follows:
 
SAXReader reader = new SAXReader();
reader.getXMLReader().setContentHandler(new MyContentHandler);
Class beforeReadHandler = reader.getXMLReader().getContentHandler();
reader.read(file);
Class afterReadHandler = reader.getXMLReader().getContentHandler();
 
!!!   afterReadHandler != beforeReadHandler   !!!
 
reader.read(file) resets the ContentHandler to some default handler. In my case, this is
afterReadHandler.getClass() == org.dom4j.io.SAXContentHandler.
 
Does anyone know how to prevent reader.read() from doing this?
 
Franz
 
----- Original Message -----
From: Franz Beil
Sent: Monday, March 25, 2002 4:26 PM
Subject: [dom4j-user] configuring the SAXParser

Hi,
 
I'm trying to configure my SAXReader with a special parser ContentHandler in the following way:
        mySAXReader.getXMLReader().setContentHandler(new CSH());
 
(CSH() implements ContentHandler; the parser I'm using is apache.crimson.parser.XMLReaderImpl)
 
Although my CSH content handler is set, it seems to be lost when reading input, i.e. it doesn't do anything, none of the implemented methods is called.
 
Did anybody experience something similar? Is there a recommended workaround?
 
Thanks a lot for help and suggestions,
Franz

Reply via email to