|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #54792 Constructor not called, but destructor is.
Submitted: 2011-05-17 15:19 UTC Modified: -
From: RQuadling at GMail dot com Assigned:
Status: Open Package: SOAP related
PHP Version: 5.3.6 OS: Windows XP SP3
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2011-05-17 15:19 UTC] RQuadling at GMail dot com
When using SOAPClient with WSDL types as PHP classes, you define the 
relationship in the classmap element of the options parameter to the SoapClient 

The instances that are created by the SOAPClient do not call the constructor, 
but, once created, the destructor is called as part of the script shutdown.

I don't know if this is a bug in SOAPClient in that it SHOULD call the 
constructors, or just a documentation issue in that the lack of construction is 
not documented.

If a PHP class with methods is used in the class map, the class is instantiated 
and you can call the methods, so it looks just like a normal class/object. But 
with no constructor.

When the script closes, the destructors are called.

My test script is fairly large as there are 14 magic methods to add to the 

So, it is available at

Test script:

Expected result:
ConversionRate::__construct ( a:0:{} )
ConversionRateResponse::__contruct ( a:0:{} )

ConversionRateResponse::__destruct ( a:0:{} )
ConversionRate::__destruct ( a:0:{} )

Actual result:
ConversionRate::__construct ( a:0:{} )

ConversionRateResponse::__destruct ( a:0:{} )
ConversionRate::__destruct ( a:0:{} )


Add a Patch

Pull Requests

Add a Pull Request

PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Sun Mar 29 16:01:24 2020 UTC