("" === NULL) = false. Even PHP knows that.
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.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Scott Mattocks
Sent: Wednesday, October 22, 2008 11:44 AM
To: 'PHP List'
Subject: Re: [UPHPU] SoapClient woes
Beau Scott wrote:
> A colleague was able to make a reallllllly dirt workaround in modifying
the
> actual XML of the request to include the nil property, but come on...
there
> has to be an easier method
> // Null param working, but very cumbersome
> $cl->getCatgories (new SoapVar('<ns1:parentId xsi:nil="true"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; />', XSD_ANYXML),
"1")
This is one of the fun things about strongly typed languages. We
recently had to modify our WSDL to allow Java clients to use our web
service. Java clients are very picky about types. If the WSDL says
string, it will be string regardless of what you send.
--
Scott Mattocks
Author: Pro PHP-GTK
http://www.crisscott.com
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net
