Issue Type: Improvement Created: 2010-07-14T08:19:50.000+0000 Last Updated: 2012-11-20T21:37:26.000+0000 Status: Open Fix version(s): Reporter: Richard Quadling (rquadling) Assignee: None Tags: - Zend_Soap_Wsdl
Related issues: - ZF-6347
The Auto Discovery process happily identifies all the properties of a complexType.
One of the issues I've come across is that some of the time, the properties will be null and the attribute xsi:nil="true" will be used for the element in the response.
This seems to be an issue for .NET clients. Sometimes. I think it only relates to specific types (xsd:dateTime for example).
By having the attribute nillable="true" in the WSDL file, then the response's nil attribute all ties up.
How do I proceed from here? I assume someone wise here will review this?
Posted by Renan de Lima (renanbr) on 2010-09-09T12:44:37.000+0000
could you send wsdl files? both, the one that works and the other one just to check complex type attributes
.net clients/servers have a problem with xsi:nil, they use this att to show up that an attribute actually does not exist, there is another notation to send a null value
nillable looks like a nice workaround for this issue, but remember this one can't be used with xsi:nil when nillable is false value is false
Have you found an issue?
See the Overview section for more details.