Bug #25607: Reflection Service does not save emerged class reflections - TYPO3.Flow - TYPO3 Forge

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

Bug #25607

Reflection Service does not save emerged class reflections

Added by Robert Lemke over 4 years ago. Updated over 4 years ago.

Status:

Resolved

Start date:

2011-03-31

Priority:

Should have

Due date:

Assigned To:

Robert Lemke

% Done:

100%

Category:

Core

Target version:

TYPO3 Flow Base Distribution - 1.0 beta 1

PHP Version:

Complexity:

Has patch:

Affected Flow version:

Description

Because the Reflection Service was not correctly connected to the bootstrap shutdown emerged classes (which were not automatically
registered during compile time) were not saved into the cache and therefore reflected again on every run.

Associated revisions

Revision 3353765d
Added by Robert Lemke over 4 years ago

[+BUGFIX] Reflection Service does not save emerged class reflections

Because the Reflection Service was not correctly connected to the
bootstrap shutdown emerged classes (which were not automatically
registered during compile time) were not saved into the cache and
therefore reflected again on every run.

This patch introduces new signals into the bootstrap and Core Command
controller and makes connects the Reflection Service's saveToCache()
method to one of the new signals.

This bug fix was auctioned at the T3BOARD11 bug auction by wildside.dk

Change-Id: I25d94f6ea84dfa84ea29aed830c71c3bbe183079
Resolves: #25607