Hint at wrong usage of @ORM\MappedSuperclass not displayed
Doctrine 2 allows usage of @MappedSuperclass without @Entity, but in FLOW3 @Entity annotation is necessary. That's why the hint was added (http://forge.typo3.org/issues/27285).
Nowadays this behaviour is broken, because TYPO3\FLOW3\Reflection\ReflectionService::ensureAggregateRootInheritanceChainConsistency() is executed before the first call to Flow3AnnotationDriver::getClassSchema() and fails.
Proposed solution: add check to ensureAggregateRootInheritanceChainConsistency() do not try to check aggregate roots for schema-less objects.
It is however highly probable that sooner or later this same problem will happen again, so it may be advisable to deal with it in better way.
Updated by Karsten Dambekalns about 9 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
I consider this solved with https://review.typo3.org/#/q/I5c617cbc28b02db1e3b7389f963fd1ab50b3cf3b,n,z