note 87789 deleted from function.soap-soapclient-soapcall by danbrown
| From: | danbrown@php.net | Date: | Mon, 22 Dec 2008 01:16:42 +0000 |
| Subject: | note 87789 deleted from function.soap-soapclient-soapcall by danbrown | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-148438@lists.php.net to get a copy of this message | ||
Note Submitter: Anonymous
----
In response to ryan's comment, I thought I would mention I solved passing XMLNode (actually
XMLElement) objects in and out of an ASP.NET WebService by defining custom XML serializers and
deserialisers to the SoapClient constructors as a "typemap" option that mapped DOMElements
back and forth via "xml_to" and "xml_from" by latching on to the provided WSDL
types. Incidentally, this seemed the only clean way to do this as the WSDL seemed to specify
<xsd:any> types for these and there does not seem to be any other serialization
"pickling" hooks for defining such. Unfortunately, this seems to be lightly documented at
best (some of the best "documentation" for this came from the PHP SOAP extension
regression test suites that are in the extension code).