i can imagine that instead of using the constructor, the __wakeup method is called.

Please try using this CVS snapshot:

  http://snaps.php.net/php5.2-latest.tar.gz
 
For Windows:

  http://windows.php.net/snapshots/

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Hi Jani,

i strumbled over this issue and have the same bug here.
tested with latest 5.2snap. Results in a not called constructor or other magic function.

the __destructor will be called but this is too late for handling special stuff here.

changed status because this bug still exists and is reproduced

__wakeup is not called before deserialization from session (if you store object in session of course). Only __set is called when setting properties.

Bug still found in PHP 5.3.2.

Same thing applies to SoapServer as well.

Same problems happens with PHP 5.3.6 (dotdeb version) on Lenny.

This is quite annoying as we cannot later call the created object's methods due to some logic done in the constructor (such as sanitizing for instance) which is missing.

Same here with 5.3.10. Maybe such classes should implement some specific 
interface (to avoid situation when class constructor has some required 
arguments) and to add some extra functionality, e.g:

<?php

interface SoapResult {
  public function __construct();
  public function afterDeserialize();
}

?>

This is not a bug. It's quite normal.

The soap object is created on the server side. So the constructor is just called on the server.
Note: This is not a technical question - the programmers of Soap-PHP just couldn't implement it. It's against the principle of webserivces.

Logical on the client no __construct neither __wakeup is called.
On the other hand no __destruct neither __sleep is called on the server - but on the client.


If you want to initialize some data after receiving the soap object, you have to use a conventional function.
"webservice objects" are NEVER created on the client side!

Still a problem on PHP 5.5.21-1+deb.sury.org~precise+2

Neither __construct nor __wakeup is called.

@miceleparkip The server doesn't create objects, it sends XML. The client decodes that XML and creates the objects. Source: http://lxr.php.net/xref/PHP_5_5/ext/soap/php_encoding.c#1479 (I think)

It's even weirder than just that. This will fail silently, no errors, just no results:

====
class MySoapObject {}

abstract class MyAppointment extends MySoapObject {
  abstract function getLabel();
}

class MyClientAppointment extends MyAppointment {
  // NO implementation of getLabel()
}

$soap = new SoapClient($wsdl, array('classmap' => array('Appointment' => 'MyClientAppointment')));
$appointments = $soap->GetAppointmentsList(array('foo' => 'bar'));
====

$appointments will be FALSE or NULL. No errors. The reason is that `MyClientAppointment` doesn't implement `getLabel()`. I would have expected a very fatal error about that missing implementation. After implementing `getLabel()`, it works like a charm. Normal PHP would complain about this, wouldn't it?

'classmap' really needs normal object instantiation...