Problems with constructor arguments and DI in non-adviced constructor interceptors
|Priority:||Should have||Due date:|
|Assignee:||Robert Lemke||% Done:||
|Target version:||TYPO3 Flow Base Distribution - 0.1|
|Has patch:||FLOW3 version affected:|
A constructor argument of a target class will end up correctly in the proxy class (ie. the proxy class builder works). However, the component configuration does not contain that argument but only the componentManager argument which was added by the AOP framework. The result is that autowiring does not work anymore (as the required original argument is not known to the object builder) and the component manager is injected instead of the expected first argument.
Updated by Robert Lemke almost 6 years ago
- Status changed from New to Closed
- Sprint set to fixed
- Framework: (Utility) Fixed a bug in the Files part: used $this instead of self.
- Framework: (Component) Improved and properly documented the ManagerAwareAspect
- Framework: (AOP) Added exposing tests for and fixed problems with constructor arguments and DI in non-adviced constructor interceptors. Fixes #60.