SAX parser: Ignoring special characters

前端 未结 4 683
说谎
说谎 2020-12-07 01:41

I\'m using Xerces to parse my XML document. The issue is that XML escaped characters like   appear in characters() method as non-escap

相关标签:
4条回答
  • 2020-12-07 01:59

    The temporary solution:

    public void startEntity(String name) throws SAXException {
        inEntity = true;
        entityName = name;
    }
    
    public void characters(char[] ch, int start, int length) throws SAXException {
        String data;
        if (inEntity) {
            inEntity = false;
            data = "&" + entityName + ";";
        } else {
            data = new String(ch, start, length);
        }
        //TODO do something instead of System.out
        System.out.println(data);
    }
    

    But still need elegant solution.

    0 讨论(0)
  • 2020-12-07 02:07

    If you supply a LexicalHandler as a callback to the SAX parser, it will inform you of the start and end of every entity reference using startEntity() and endEntity() callbacks.

    (Note that the JavaDoc at http://download.oracle.com/javase/1.5.0/docs/api/org/xml/sax/ext/LexicalHandler.html talks of "entities" when the correct term is "entity references").

    Note also that there is no way to get a SAX parser to tell you about numeric character references such as ሴ. Applications are supposed to treat these in exactly the same way as the original character, so you really shouldn't be interested in them.

    0 讨论(0)
  • 2020-12-07 02:14

    There is one more may: escapeXml method of org.apache.commons.lang.StringEscapeUtils class.

    Try this code in your characters(char[] ch, int start, int length) method:

    String data=new String(ch, start, length);
    String escapedData=org.apache.commons.lang.StringEscapeUtils.escapeXml(data);
    

    You may download the jar here.

    0 讨论(0)
  • 2020-12-07 02:15

    I think your solution is not too bad: a few lines of code to do exactly what you want. The problem is that startEntity and endEntity methods are not provided by ContentHandler interface, so you have to write a LexicalHandler which works in combination with your ContentHandler. Usually, the use of an XMLFilter is more elegant, but you have to work with entity, so you still should write a LexicalHandler. Take a look here for an introduction to the use of SAX filters.

    I'd like to show you a way, very similar to yours, which allows you to separate filtering operations (wrapping & to & for instance) from output operations (or something else). I've written my own XMLFilter based on XMLFilterImpl which also implements LexicalHandler interface. This filter contains only the code related to entites escape/unescape.

    public class XMLFilterEntityImpl extends XMLFilterImpl implements
            LexicalHandler {
    
        private String currentEntity = null;
    
        public XMLFilterEntityImpl(XMLReader reader)
                throws SAXNotRecognizedException, SAXNotSupportedException {
            super(reader);
            setProperty("http://xml.org/sax/properties/lexical-handler", this);
        }
    
        @Override
        public void characters(char[] ch, int start, int length)
                throws SAXException {
            if (currentEntity == null) {
                super.characters(ch, start, length);
                return;
            }
    
            String entity = "&" + currentEntity + ";";
            super.characters(entity.toCharArray(), 0, entity.length());
            currentEntity = null;
        }
    
        @Override
        public void startEntity(String name) throws SAXException {
            currentEntity = name;
        }
    
        @Override
        public void endEntity(String name) throws SAXException {
        }
    
        @Override
        public void startDTD(String name, String publicId, String systemId)
                throws SAXException {
        }
    
        @Override
        public void endDTD() throws SAXException {
        }
    
        @Override
        public void startCDATA() throws SAXException {
        }
    
        @Override
        public void endCDATA() throws SAXException {
        }
    
        @Override
        public void comment(char[] ch, int start, int length) throws SAXException {
        }
    }
    

    And this is my main, with a DefaultHandler as ContentHandler which receives the entity as it is according to the filter code:

    public static void main(String[] args) throws ParserConfigurationException,
            SAXException, IOException {
    
        DefaultHandler defaultHandler = new DefaultHandler() {
            @Override
            public void characters(char[] ch, int start, int length)
                    throws SAXException {
                //This method receives the entity as is
                System.out.println(new String(ch, start, length));
            }
        };
    
        XMLFilter xmlFilter = new XMLFilterEntityImpl(XMLReaderFactory.createXMLReader());
        xmlFilter.setContentHandler(defaultHandler);
        String xml = "<html><head><title>title</title></head><body>&amp;</body></html>";
        xmlFilter.parse(new InputSource(new StringReader(xml)));
    }
    

    And this is my output:

    title
    &amp;
    

    Probably you don't like it, anyway this is an alternative solution.

    I'm sorry, but with SaxParser I think you don't have a more elegant way.

    You should also consider switching to StaxParser: it's very easy to do what you want with XMLInputFactory.IS_REPLACING_ENTITY_REFERENCE set to false. If you like this solution, you should take a look here.

    0 讨论(0)
提交回复
热议问题