Bug #27045

Introduced properties are not available in the reflection service during a compile run

Added by Andreas Förthner over 10 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
AOP
Target version:
-
Start date:
2011-05-26
Due date:
% Done:

0%

Estimated time:
PHP Version:
Has patch:
Complexity:

Description

The AOP proxy builder must register each introduced property, that the other proxy builders can use the reflection service to ask for them...

Related issues

Related to TYPO3.Flow - Bug #39413: AOP: Property introduction seems to be brokenResolvedRobert Lemke2012-07-31

Actions
Related to TYPO3.Flow - Feature #37373: Make annotation overrides / "injection" via Objects.yaml possibleUnder ReviewMarc Neuhaus2012-05-21

Actions
Related to TYPO3.Flow - Bug #51188: Doctrine does not respect AOP-injected propertiesNew2013-08-19

Actions
#1

Updated by Sebastian Kurfuerst about 10 years ago

  • Target version set to 1230
#2

Updated by Christopher Hlubek about 10 years ago

I think this is not only during the compile run, but also after the compilation. An introduced property will not be returned by the ReflectionService (e.g. getPropertyNamesByTag).

#3

Updated by Karsten Dambekalns almost 10 years ago

  • Target version deleted (1230)
#5

Updated by Alexander Berl over 8 years ago

One could classSchema->addProperty in ProxyClassBuilder->buildProxyClass for every introduced property. However, the type information isn't available at that point unless the docblock is parsed there also.

Wouldn't it be possible to do a whole reflectionData update for all classes with introduced properties at last? The problem I see is that the class is already loaded with the unproxied status, so just calling the reflection won't help. So the reflection would have to be called in it's own command/process AFTER the proxy is built.

Also available in: Atom PDF