Wilson Wu

The issue is really with Exchange server side that if your mail contains invalid XML characters EWS will just send it back. And the exception is raised from JDK's XMLStreamReaderImpl.

Yeah if MS is not able to fix then we need to have a clean InputStream. That's actually handled in their .Net managed API. And again EWS is not accepting...

While intercepting InputStream is a way that could be quite expensive when dealing with large XML response to filter out things like &#1A; Interestingly I noticed most these characters are...

So, I got this resolved in a pretty much hacking way. I'm not so happy about this as basically you need to copy quite a few OpenJDK JAXP code inside...