StreamingSubscriptionConnection.close() calls HttpWebRequest.close() which will first
attempts to consume the response before releasing the connection. This unfortunately
will hang since the notification reader thread is still blocked reading from the same
connection. The fix is to just the connection without consuming the response entity.

…y default (from #353)

- Add a unit test (taken from e7b7505)

…T to just 2.0

…d by the JVM is not Xerces

…e JVM has been configured to use another one

…ava-api

See this commit:
RavnSystems@845f20f

and this issue:
#353

Looks like exchange does not properly excape some XML chars
when present in email. There seems to be a way to allow unicode
by forcing "Xml 1.1" instead of "Xml 1.0" but this is reported
to not work in some versions of exchange.

Skip over invalid xml