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.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web2

  • via Coderanch by sahiem shaikh, 7 months ago
    org.xml.sax.SAXParseException: An inv alid XML character (Unicode: 0x15) was found in the element content of the docum ent.
  • via coderanch.com by Unknown author, 1 year ago
    org.xml.sax.SAXParseException: An inv alid XML character (Unicode: 0x15) was found in the element content of the docum ent.
  • Stack trace

    • 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(BaseProxy.java:236) at com.trigent.ws.proxy.CustomProxy.find(CustomProxy.java:188) at com.trigent.ws.proxy.CustomProxy.execute(CustomProxy.java:54)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.