Bug #34545
Hint at wrong usage of @ORM\MappedSuperclass not displayed
| Status: | Resolved | Start date: | 2012-03-05 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Persistence | |||
| Target version: | TYPO3 Flow Base Distribution - 1.1 RC1 | |||
| PHP Version: | Complexity: | easy | ||
| Has patch: | No | Affected Flow version: | FLOW3 1.1.0 beta 1 |
Description
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.
Related issues
History
#1 Updated by Karsten Dambekalns over 3 years ago
- Category set to Persistence
- Status changed from New to Accepted
- Assigned To set to Karsten Dambekalns
- Target version set to 1.1
#2 Updated by Karsten Dambekalns about 3 years ago
- Target version changed from 1.1 to 1.1 RC1
#3 Updated by Karsten Dambekalns about 3 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
- Affected Flow version changed from Git master to FLOW3 1.1.0 beta 1
I consider this solved with https://review.typo3.org/#/q/I5c617cbc28b02db1e3b7389f963fd1ab50b3cf3b,n,z