Solve the problem of sequentialization and reverse sequence type in GSOAP development (No Deserializer Found to DeSerialize)

xiaoxiao2021-04-07  318

Developed with GSOAP, the Client End Test program of Google Search is jumped out of the following error "No Deserializer Found to DeSerialize A ': key' using eNCoding style 'http://schemas.xmlsoap.org/soap/encoding/'." KEY is exactly a parameter I passed to the server. I found a similar problem in Google. I have a big pile in theory. The whole is in the serialization and reverse sequence. The problem has a problem that the type does not match, but it has not given a specific solution. If you don't go around the bend, you will directly list the solution: add the parameter -T, just when you compile the header file, it is as simple as it! If you solve your problem, I hope you can top.

This is the XML data before adding parameters - T:

d1qfhllv3ntr / zfw2j23gy2v0kp

This is the XML data after adding parameters:

D1qfhllv3ntr / zfw2j23gy2v0kp

You should notice: The second data plus the XSI: Type = "XSD: String"

转载请注明原文地址:https://www.9cbs.com/read-132438.html

New Post(0)