On Thu, 31 Mar 2005, George Schlossnagle wrote: > Are there any feelings (or perhaps just an undocumented way) to force a > default namespace on SOAP payload? I'm looking at integrating with a > SOAP server that has a slightly broken parser, and seems to need to > have the payload in a default namespace rather than explicitly > namespaced. I.e. rather than: Ew. I guess this is a question of interop versus standards. In general, I would prefer not to kludge up the extension to work around obviously broken SOAP servers. However, at a higher level, the whole point of the extension is to enable people to easily communicate with servers -- even ones they cannot control. I'm taking this is a major SOAP service, and there's little chance of getting them to fix their server not to be brain-dead? -adam -- adam@trachtenberg.com | http://www.trachtenberg.com author of o'reilly's "upgrading to php 5" and "php cookbook" avoid the holiday rush, buy your copies today! -- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
