org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x15) was found in the element content of the document. DefaultValidationEventHandler: [FATAL_ERROR]: An invalid XML character (Unicode: 0x15) was found in the element content of the document. Location:

hivmr.com | 9 months ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    db:: 4.35::An invalid XML character (Unicode: 0x0) was found in the prolog of the docu 8s

    hivmr.com | 9 months ago
    org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x15) was found in the element content of the document. DefaultValidationEventHandler: [FATAL_ERROR]: An invalid XML character (Unicode: 0x15) was found in the element content of the document. Location:
  2. 0

    An invalid XML character (Unicode: 0x15) was found  ERROR

    Oracle Community | 1 decade ago | 843834
    org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x15) was found in the element content of the document. DefaultValidationEventHandler: [FATAL_ERROR]: An invalid XML character (Unicode: 0x15) was found in the element content of the document. Location:
  3. 0

    Struts mapping exception

    Stack Overflow | 4 years ago | 123Ex
    org.xml.sax.SAXParseException: The content of element type "action-mappings" must match "(action)*".
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Re: encoding problem

    ws-wsif-user | 1 decade ago | Aleksander Slominski
    org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x4) was found in the element content of the document.
  6. 0

    The following information is printed when I try to parse an XML file saved in UTF-8 BOM format: org.xml.sax.SAXParseException: Content is not allowed in prolog. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) If I save the very XML file to standard UTF-8 format then everything works smoothly. I've tried to debug the source code of Xecers. I found that Xecers actually has codes that handle UTF-8 BOM formatted input stream in class org.apache.xerces.impl.XMLEntityManager.java (@version $Id: XMLEntityManager.java,v 1.94 2005/04/19 03:18:18 mrglavas Exp $). But those codes has never been executed in my case. The following is the detail: In public method setupCurrentEntity() in class XMLEntityManager, there are several lines of codes which dealing with UTF-8 BOM format input stream, and all those codes are located in the code block starting from line 929 if ( reader == null ) { .... }. The "reader" in the if clause is defined in line 923. And In my case, the reader would not be assigned a "null" value so that the codes which dealing with UTF-8 BOM would never been executed.

    Apache's JIRA Issue Tracker | 1 decade ago | lin zhu
    org.xml.sax.SAXParseException: Content is not allowed in prolog.

  1. rp 1 times, last 4 months ago
4 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. org.xml.sax.SAXParseException

    An invalid XML character (Unicode: 0x15) was found in the element content of the document. DefaultValidationEventHandler: [FATAL_ERROR]: An invalid XML character (Unicode: 0x15) was found in the element content of the document. Location:

    at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException()
  2. Xerces2-j
    AbstractSAXParser.parse
    1. org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:232)
    2. org.apache.xerces.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:213)
    3. org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:385)
    4. org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:315)
    5. org.apache.xerces.impl.XMLScanner.reportFatalError(XMLScanner.java:1294)
    6. org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1500)
    7. org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:348)
    8. org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:539)
    9. org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:595)
    10. org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
    11. org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1125)
    11 frames
  3. grants.impl.runtime
    UnmarshallerImpl.unmarshal
    1. grants.impl.runtime.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:142)
    1 frame
  4. Java RT
    AbstractUnmarshallerImpl.unmarshal
    1. javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:131)
    2. javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:178)
    2 frames
  5. Unknown
    Transfer.main
    1. Transfer.main(Transfer.java:20)
    1 frame