Bug #30467: Doctrine fails to initialize AOP and DI in some cases - TYPO3.Flow - TYPO3 Forge

TYPO3 Flow Base Distribution TYPO3.Eel TYPO3.Flow TYPO3.Fluid TYPO3.Kickstart TYPO3.Welcome Packages Applications

Bug #30467

Doctrine fails to initialize AOP and DI in some cases

Added by Andreas Förthner almost 4 years ago. Updated over 3 years ago.

Status:

Resolved

Start date:

2011-09-30

Priority:

Should have

Due date:

Assigned To:

Andreas Förthner

% Done:

100%

Category:

Persistence

Target version:

TYPO3 Flow Base Distribution - 1.0.2

PHP Version:

Complexity:

Has patch:

Affected Flow version:

FLOW3 1.0.0

Description

When a Doctrine lazy loading proxy for an object is created for some specific purpose (e.g. when initializing session objects relating to an entity) but filled afterwards "on the fly" if this object is part of a wide range "findBy" call through some query, Doctrine initializes the lazy loading proxy but does not call __wakeup and therefore not initialize AOP and DI.

Associated revisions

Revision 3b704952
Added by Lienhart Woitok over 3 years ago

[BUGFIX] Doctrine@PostLoad calls DI and AOP initialization explicitly.

When a Doctrine lazy loading proxy for an object is
created for some specific purpose (e.g. when initializing
session objects relating to an entity) but filled afterwards
"on the fly" if this object is part of a wide range "findBy"
call through some query, Doctrine initializes the lazy
loading proxy but does not call __wakeup and therefore not initialize AOP and DI.
We work around this issue, by initializing those objects
with a Doctrine PostLoad hook explicitly.

Change-Id: I83ba6484e9daecf5344242815ec52ad1770907f9
Resolves: #30467
Releases: 1.1