Bug #31042: Throwing an exception throws an exception.... - TYPO3.Flow - TYPO3 Forge

Bug #31042

Throwing an exception throws an exception....

Added by Adrian Föder over 9 years ago. Updated over 9 years ago.

Status:

Resolved

Priority:

Must have

Assignee:

Karsten Dambekalns

Category:

Reflection

Target version:

TYPO3 Flow Base Distribution - 1.0.0

Start date:

2011-10-18

Due date:

% Done:

100%

Estimated time:

PHP Version:

Has patch:

Complexity:

Description

after running the master branch intended to become RC1, I have Uncaught Exception in FLOW3 #1: Warning: current() expects parameter 1 to be array, null given in [...]Packages\Framework\TYPO3.FLOW3\Classes\Reflection\ReflectionService.php line 932. The mentioned line is

throw new \TYPO3\FLOW3\Reflection\Exception(sprintf('Classes tagged as entity or value object must be of scope prototype, however, %s is declared as %s.', $className, current($classTagValues)), 1264103349);

In fact, the $classTagValues variable is not set in this function.

Updated by Adrian Föder over 9 years ago

..maybe the current() invocation should be replaced with $scopeAnnotation->value, so that the whole block should read

if ($scopeAnnotation !== NULL && $scopeAnnotation->value !== 'prototype') {
    throw new \TYPO3\FLOW3\Reflection\Exception(sprintf('Classes tagged as entity or value object must be of scope prototype, however, %s is declared as %s.', $className, $scopeAnnotation->value), 1264103349);
}