Project

General

Profile

Actions
Copy link

Bug #67402

closed

Document "__wakeup" no longer called in AbstractDomainObjects as breaking (?)

Added by Christian Kuhn over 9 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Christian Kuhn
Category:
-
Target version:
7.3 (Packages)
Start date:
2015-06-10
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Stabilization Sprint

Description

with the instantiator patch __wakeup() is no longer called on re-constituting AbstractDomainModel objects from db. This might be breaking ... also, the default implementation __wakeup and the empty initializeObject() in

https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/extbase/Classes/DomainObject/AbstractDomainObject.php#L69

are obsolete. In case we decide to remove _wakeup() altogether (probably a good idea), any own __wakeup() method implementation extending AbstractDomainObject will fatal in case it calls parent::_wakeup as documented currently. This would be a breaking change then and should be documented accordingly.

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Bug #66473: Cannot create object implementing Serializable on PHP 5.6ClosedMathias Brodala2015-04-17

Actions
Related to TYPO3 Core - Bug #61044: AbstractDomainObject::__wakeup() method should not call initializeObject method internallyClosedDaniel Hürtgen2014-08-18

Actions
Actions
Copy link

Also available in: Atom PDF