php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #30928 When Using WSDL, SoapServer doesn't handle private or protected properties
Submitted: 2004-11-29 05:45 UTC Modified: 2004-12-07 18:30 UTC
From: david at giffin dot org Assigned: dmitry (profile)
Status: Closed Package: SOAP related
PHP Version: 5CVS-2004-11-29 (dev) OS: Linux
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: david at giffin dot org
New email:
PHP Version: OS:

 

 [2004-11-29 05:45 UTC] david at giffin dot org 
Description:
------------
When using WSDL with a complex type definition the SoapServer doesn't handle static, private or protected properties correctly. SoapServer returns a SoapFault: "SOAP-ERROR: Encoding: object hasn't 'xxxx' property." Where 'xxxx' is the property defined as static, private or protected.

FYI: This bug is similar to Bug #30799. Bug #30799 is fixed when returning a user defined object, which is not defined in the WSDL.

Reproduce code:
---------------
I can post some code if you need it. It would be too much code for this form.

Expected result:
----------------
The SoapServer would return the data present in the static, private or protected property if it is defined as an element for the complexType defined in the WSDL.

Actual result:
--------------
The SoapServer returns a SoapFault: "SOAP-ERROR: Encoding: object hasn't 'xxxx' property."

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2004-12-07 18:30 UTC] dmitry@php.net 
Fixed in CVS HEAD and PHP_5_0.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Mon Dec 30 14:01:28 2024 UTC