Looking through the 2.2 source, it appears that RPCMessage::unmarshal
works out the correct encodingStyle URL, but then passes the wrong
version to the call constructor. This doesn't trip up the Apache
client because RPCRouter::invoke will pull the encodingStyle from the
first child of the body if
I'm trying to call the Apache SOAP 2.2 sample
AddressBook::getAllListings, which is a literal XML request/response.
The Apache based client works, the equivalent pocketSOAP code produces
an error, i can't see why,
Here's the Apache generated request that works
http://schemas.xmlsoap.org/soap/en
