[UPHPU] SoapClient woes

[Scott Mattocks]

Beau Scott wrote:
> ("" === NULL) = false. Even PHP knows that.

The problem is that Java is expecting a string and you are sending NULL. 
NULL is not a string. Not in any language. With Java if you tell it to 
expect a string, it expects a string and nothing else will do. If you 
tell it to expect a string or null (with nil="true") it will be smart 
enough to handle the value correctly.

> I don't think this isn't a strongly-typed vs loosely-typed issue, this is an
> issue of SoapClient transforming NULL to an empty string rather than
> following the soap standard and setting the xsi:nil attribute to true as it
> should when building the SOAP vars out.

Java is pickier than most. We had people build all sorts of clients for 
our API and never had a problem until someone tried building a Java 
client. PHP and .NET never had problems.

Are you able to capture your outgoing XML from the server and see what 
it looks like? Make sure the XML you are sending back matches the WSDL.