ID: 41151
Updated by: [EMAIL PROTECTED]
Reported By: m dot necib at akrobat dot fr
-Status: Assigned
+Status: Feedback
Bug Type: SOAP related
Operating System: Windows XP
PHP Version: 5.2.1
Assigned To: dmitry
New Comment:
I just committed test file ext/soap/tests/schema/schema085.phpt, that
demonstrates proper element ordering. In your example you probably do
somthing wrong. I cannot say that exactly is wrong as you didn't provide
full reproduce case, probably you object isn't encoded using WSDL.
In case if you like me to look into problem please provide full example
(without ...) including full WSDL file.
Previous Comments:
------------------------------------------------------------------------
[2007-04-20 16:55:19] m dot necib at akrobat dot fr
WSDL :
<complexType name="A">
<sequence>
<element name="a" type="xsd:int"/>
</sequence>
</complexType>
<complexType name="B">
<complexContent>
<extension base="impl:A">
<sequence>
<element name="b" type="xsd:int"/>
</sequence>
</extension>
</complexContent>
</complexType>
------------------------------------------------------------------------
[2007-04-20 16:47:37] m dot necib at akrobat dot fr
Description:
------------
When using subclass as a value in WSDL mode,
the properties are written in the wrong order :
the child class properties are written _before_
the parent properties.
Reproduce code:
---------------
PHP:
class A
{
public $a ;
}
class B extends A
{
public $b ;
}
$client = new SoapClient(...) ;
$var = new SoapVar( new B(), SOAP_ENC_OBJECT, 'B', 'http://myns/' ) ;
$client->foo($var) ;
Expected result:
----------------
SOAP request :
<parametres xsi:type="B" >
<a></a>
<b></b>
</parametres>
Actual result:
--------------
SOAP request :
<parametres xsi:type="B" >
<b></b>
<a></a>
</parametres>
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=41151&edit=1
