Per w3.org's own doc on XML http://www.w3.org/TR/REC-xml/#charencoding....
In the absence of information provided by an external transport protocol (e.g. HTTP or MIME), it is a fatal error for an entity including an encoding declaration to be presented to the XML processor in an encoding other than that named in the declaration, or for an entity which begins with neither a Byte Order Mark nor an encoding declaration to use an encoding other than UTF-8. Note that since ASCII is a subset of UTF-8, ordinary ASCII entities do not strictly need an encoding declaration.
But the code in that method (and other places) (plus the explicit comment " No special encoding type found. Answer the stream as is ") ignore this requirement and process the XML in whatever the code page of the system is in.
An example is this SOAP payload that only indicates the xml version:
<?xml version="1.0" ?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body>.......and so on.
The additional twist is that the HTTP header for the web service call DID respond with an encoding but that doesn't get passed in to the AbtXmlMappingParser methods.
HTTP/1.1 200 OK
Date: Mon, 14 Jun 2010 23:27:26 GMT