Bug #40318 [Com]: SOAP_ENC_OBJECT does not encode object properties with namespace

Edit report at https://bugs.php.net/bug.php?id=40318&edit=1 ID: 40318 Comment by: jasminedisouza70 at gmail dot com Reported by: bink at eezi dot net dot au Summary: SOAP_ENC_OBJECT does not encode object properties with namespace Status: Not a bug Type: Bug Package: SOAP related Operating System: Redhat PHP Version: 5.2.0 Assigned To: dmitry Block user comment: N Private report: N New Comment: IPRIMUS is providing their customers with the good economic and residential internet packages as well as mobile service. IPRIMUS proposal a dimension of products and services, starts from NBN wireless and TiVO to assure for internet security. Along with the imperative features, it also provides pliable plans, mobile protection and inclusion maps. If you want to know more about the product then you can access to the official site of the iPRIMUS. There you will gain the correct resolution to every question. Although, iPRIMUS face some technical issue while using the internet service. But, fortunately, you are capable with resolution also to fix those problems. Users are supported by IPRIMUS Tech Support which exist of minded team found after roaming around the world. https://www.helpdeskaustralia.com/iprimus-customer-service.html Previous Comments: ------------------------------------------------------------------------ [2007-03-30 09:37:01] dmitry@php.net Without WSDL file ext/soap cannot know that "val1" element must be namespace qualified and it cannot guess which namespace to use. WSDL file may specify the encoding rules for the soap header, but without WSDL we must not add any namespace. If you really need namespace qualification, but don't declare SOAP header in WSDL file, you can add namespaces manually using SoapVar. Replace header constructor with the following code and you will get that you like (or write proper WSDL). class headers { function __construct($val1, $val2){ $this->val1 = new SoapVar($val1, XSD_STRING, NULL, NULL, "val1", "http://url.com/namespace2"); $this->val2 = new SoapVar($val2, XSD_STRING, NULL, NULL, "val1", "http://url.com/namespace2"); } } ------------------------------------------------------------------------ [2007-02-16 02:11:50] bink at eezi dot net dot au The WSDL shouldn't affect the encoding, unfortunately due to NDA issues, I can't send it to you... The error can be replicated with or without wsdl operation, the namespace still isn't set for object properties when the object is encoded with a namespace. ------------------------------------------------------------------------ [2007-02-15 10:51:03] dmitry@php.net Pleaseprovide the WSDL file. I am not able to check your example without it. ------------------------------------------------------------------------ [2007-02-06 00:45:18] bink at eezi dot net dot au I'm not able to test cvs, this is being used on our development and production servers. If there is someone else out there with a server running cvs I coule setup a trial on it to see... Just need shell access on a normal user.... ------------------------------------------------------------------------ [2007-02-05 20:38:22] tony2001@php.net Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.2-win32-latest.zip ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=40318 -- Edit this bug report at https://bugs.php.net/bug.php?id=40318&edit=1