>>When having discussed that with Microsoft, it appears that this is by design. This is the expected behavior.
>
>Expected? wierd

It is also my reaction. I guess by design is an overall representation which could include some isolated issues like this.

>Then this is a wierd expected behavior.

Claudio made some tests on that one and confirmed me that. Maybe he could provide more explanations on additional comment on this.

>Wich one? using string instead of date?

I'm not sure what you mean here. My comment was only when defining a parameter as date. As for other reaction that could happen with a string type, I don't have any idea nor having found anything else in regards to that with string. In my case, I updated our robot to check for a new version of the WSDL file. Once discovered, he'll replace in the WSDL file all occurences where xsd:datetime should be replaced with xsd:date.