From cbeef8c00dd2b879c4a45096c210530c263e0e89 Mon Sep 17 00:00:00 2001
From: mguessan <mguessan@3d1905a2-6b24-0410-a738-b14d5a86fcbd>
Date: Thu, 12 Jan 2012 21:54:06 +0000
Subject: [PATCH] EWS: Fix 3471671, workaround for Exchange invalid chars

git-svn-id: http://svn.code.sf.net/p/davmail/code/trunk@1877 3d1905a2-6b24-0410-a738-b14d5a86fcbd
---
 src/java/com/ctc/wstx/sr/StreamScanner.java | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/java/com/ctc/wstx/sr/StreamScanner.java b/src/java/com/ctc/wstx/sr/StreamScanner.java
index a1e476b9..215cc530 100644
--- a/src/java/com/ctc/wstx/sr/StreamScanner.java
+++ b/src/java/com/ctc/wstx/sr/StreamScanner.java
@@ -2383,11 +2383,11 @@ public abstract class StreamScanner
             if (value == 0) {
                 throwParseError("Invalid character reference: null character not allowed in XML content.");
             }
-            // XML 1.1 allows most other chars; 1.0 does not:
-            if (!mXml11 &&
-                (value != 0x9 && value != 0xA && value != 0xD)) {
-                reportIllegalChar(value);
-            }
+            // XML 1.1 allows most other chars; 1.0 does not: However Exchange sends such chars with XML 1.0
+            //if (!mXml11 &&
+            //    (value != 0x9 && value != 0xA && value != 0xD)) {
+            //    reportIllegalChar(value);
+            //}
         }
     }