ValidatorResolver tries to use data type as validator type
When buildMethodArgumentsValidatorConjunctions() iterates over method arguments, it tries to get a validator for each type. This works for simple types, but for objects the class name is used as validator directly. This is a) nonsense and b) causes circular dependency problems to begin with.
The problem is caused
$typeValidator = $this->createValidator($methodParameter['type']);, since createValidator() expects to get either one of the internal validator shorthands or the fully qualified name of a validator - but not a data type!
Updated by Karsten Dambekalns over 11 years ago
Bastian Waidelich wrote:
Additional note: IIRC
isObjectRegistered()on the object manager (and fires the FLOW3 autoloader) for simple types too.
isObjectRegistered() is more or less a simple isset() - no autoloader involved.