On the evening of Thursday, two colleagues at the server and client were arguing over the soap interface. The service side colleague thinks that the client's colleague sends the server the SOAP message the XML structure to have the problem, the few XML nodes, causes the servers to parse the error. And the client colleagues think that their own on the Android phone to send soap, is sent through an object, object properties and so on, see the code is set correctly, do not think it is a problem on their side.
This time, it is necessary to catch the bag positioning. The service side of the colleague, originally intended to use Wireshark to grab the bag. Another colleague at the back suggested grabbing the client, the package on the phone. Before I grabbed the bag on the phone, is to let the computer to share wireless to the mobile phone, and then mobile phone to the computer as a proxy, on the computer to grab the bag on the line. The colleague who puts forward to catch the mobile phone bag gives a good thing, tcptrace.
Tcptrace works by making the computer a proxy to handle TCP requests on the phone or other devices, so that the SOAP messages sent on the phone can be printed.
I wanted to write a little more, but there are a lot of people on the internet who have written similar things. For example: http://blog.csdn.net/maosijunzi/article/details/8259021
I'm not going to write that much. Direct sticker Download URL come out: http://www.pocketsoap.com/tcptrace/
------Gain insight at work