Consuming SOAP Web Service, error when de-serializing value types

Question

Does anybody know how I can troubleshoot web services responses? When I get my soap message back from a web service call I get this error "The string '' is not a valid AllXsd value" as soon as it's a value type like a datetime per example.

My proxy classes are generated from wsdl's using wsdl.exe, the wsdl seems valid. I have seen nothing wrong in the proxy classes (specified values are generated, datetime is nullable).

I have tried netmon to see the soap envelopes on the wire but everything seems normal.

Can you think of other ways to troubleshoot this? or maybe a clue about what is going on here?

Please post the complete exception. Catch the exception and post the result of ex.ToString(). — John Saunders
– John Saunders, Commented Jul 22, 2009 at 3:25

Luis · Accepted Answer · 2009-07-10 02:32:33Z

1

Do you have any documentation available on the web service? You report having this problem when you use datetime, verify the date is in the correct format date.ToString("yyyy-MM-dd"); or whatever your service is expecting.

answered Jul 10, 2009 at 2:32

Luis

5023 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Mehmet Aras · Accepted Answer · 2009-07-22 03:42:40Z

1

Try Web Service Studio and hit your web service with that tool to see if it is having the same problem as your client. You may gather some clues. Is the web service your code? If it is, are you using asmx or WCF? are you using a DataContract serializer or XmlSerializer? Have you tried regenerating your client proxy?

answered Jul 22, 2009 at 3:42

Mehmet Aras

5,4021 gold badge27 silver badges34 bronze badges

Comments

teebot · Accepted Answer · 2009-07-30 13:57:06Z

1

Ok I found out what the problem was.

There is 2 ways for an element to be null in SOAP:

Either with the entire element missing Or with the argument xsi:nil="true" and no value

They fixed it by modifying their message with the first option. Since then I'm able to deserialize without problems.

Thank you for your answers.

answered Jul 30, 2009 at 13:57

teebot

1,1002 gold badges13 silver badges25 bronze badges

Comments

demoncodemonkey · Accepted Answer · 2014-11-11 17:51:16Z

0

My SOAP request was returning BadRequest because of this xsi:nil="true" thing.
What fixed it was to add this to the top of the SOAP envelope:

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

For example:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://www.blahblahblah.com/myobjectdefinition" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

I don't know why SoapUI didn't generate this bit, but anyway it fixed it for me.

answered Nov 11, 2014 at 17:51

demoncodemonkey

12k10 gold badges64 silver badges105 bronze badges

Collectives™ on Stack Overflow

Consuming SOAP Web Service, error when de-serializing value types

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related