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

From: Date: Sat, 04 Jul 2020 12:44:19 +0000
Subject: Bug #40318 [Com]: SOAP_ENC_OBJECT does not encode object properties with namespace
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-227810@lists.php.net to get a copy of this message
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: Brother Printer are the best in the world and broadly used by users all across the world. However, unexpected technical problems can appear anytime while using the Brother Printers, Then ring us at our Brother Printer Support Number Australia to instantly get assist. We work as independent tech support service transfer for brother printer and have a backed by team of best-experienced and ascertain professionals. Our knowledgeable technicians fixed numerous critical or complicated Brother Printer Technical problems easily. https://www.helpdeskaustralia.com/brother-printer-customer-service.html Previous Comments: ------------------------------------------------------------------------ [2020-07-03 12:51:49] jasminedisouza70 at gmail dot com Our Lexmark Printer Customer Service Helpline Number +1-800-383-368 crazily instant solution Call Lexmark Printer Contact Support service phone number. Fix problems related to Lexmark Printer problems Call Lexmark Printer Support Number. Lexmark Printer id sometimes start to create a issue for its users and they become incapable to access their Lexmark Printer data. In that case, they should talk to the Lexmark Printer nerd who know all the possible problems that might have taken place with their financial software. Lexmark Printer Contact Service Phone Number users may call our Lexmark Printer Customer Service Number 1-800-383-368 which they may find online without any difficulty. https://www.helpdeskaustralia.com/lexmark-printer-support.html ------------------------------------------------------------------------ [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.... ------------------------------------------------------------------------ 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

« previous php.bugs (#227810) next »