Bug #27045
Introduced properties are not available in the reflection service during a compile run
| Status: | New | Start date: | 2011-05-26 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | AOP | |||
| Target version: | - | |||
| PHP Version: | Complexity: | |||
| Has patch: | FLOW3 version affected: | FLOW3 1.0.0 | ||
| Votes: | 3 (View) |
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 broken | Under Review | 2012-07-31 | ||
| related to TYPO3.Flow - Feature #37373: Make annotation overrides / "injection" via Objects.yaml ... | Under Review | 2012-05-21 |
History
Updated by Sebastian Kurfuerst almost 2 years ago
- Target version set to 1230
Updated by Christopher Hlubek over 1 year 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).
Updated by Karsten Dambekalns over 1 year ago
- Target version deleted (
1230)
Updated by Karsten Dambekalns over 1 year ago
- FLOW3 version affected set to FLOW3 1.0.0
Updated by Alexander Berl about 1 month 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.