com.trigent.exception.ProcessingException: org.xml.sax.SAXParseException: An inv alid XML character (Unicode: 0x15) was found in the element content of the docum ent.

coderanch.com | 7 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    AxisFault SAXParseException (Web Services forum at Coderanch)

    coderanch.com | 7 months ago
    com.trigent.exception.ProcessingException: org.xml.sax.SAXParseException: An inv alid XML character (Unicode: 0x15) was found in the element content of the docum ent.
  2. 0

    AxisFault SAXParseException

    Coderanch | 10 years ago | sahiem shaikh
    com.trigent.exception.ProcessingException: org.xml.sax.SAXParseException: An inv alid XML character (Unicode: 0x15) was found in the element content of the docum ent.

    Root Cause Analysis

    1. com.trigent.exception.ProcessingException

      org.xml.sax.SAXParseException: An inv alid XML character (Unicode: 0x15) was found in the element content of the docum ent.

      at com.trigent.ws.proxy.BaseProxy.invoke()
    2. com.trigent.ws
      CustomProxy.execute
      1. com.trigent.ws.proxy.BaseProxy.invoke(BaseProxy.java:236)
      2. com.trigent.ws.proxy.CustomProxy.find(CustomProxy.java:188)
      3. com.trigent.ws.proxy.CustomProxy.execute(CustomProxy.java:54)
      3 frames