Bug #34545

Hint at wrong usage of @ORM\MappedSuperclass not displayed

Added by Ondrej Hatala over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Could have
Category:
Persistence
Start date:
2012-03-05
Due date:
% Done:

100%

PHP Version:
Has patch:
No
Complexity:
easy

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

Related to TYPO3.Flow - Bug #27285: Exception with /** @MappedSuperclass */ Resolved 2011-06-07
Related to TYPO3.Flow - Bug #37547: Exception "No class schema found for "Doctrine\Common\Collections\Collection". The class should probably marked as entity or value object!" should point out which model triggers the error Resolved 2012-05-28

History

#1 Updated by Karsten Dambekalns over 7 years ago

  • Category set to Persistence
  • Status changed from New to Accepted
  • Assignee set to Karsten Dambekalns
  • Target version set to 1.1

#2 Updated by Karsten Dambekalns over 7 years ago

  • Target version changed from 1.1 to 1.1 RC1

#3 Updated by Karsten Dambekalns over 7 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF