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

Added by Michel Albers over 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Must have
Category:
Persistence
Start date:
2012-05-28
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

title says all


Related issues

Related to TYPO3.Flow - Bug #34545: Hint at wrong usage of @ORM\MappedSuperclass not displayedResolvedKarsten Dambekalns2012-03-05

Actions
#1

Updated by Karsten Dambekalns over 9 years ago

  • Project changed from 478 to TYPO3.Flow
  • Category deleted (1042)
#2

Updated by Karsten Dambekalns over 9 years ago

  • Category set to Persistence
  • Status changed from New to Accepted
  • Assignee set to Karsten Dambekalns
  • Target version changed from 1.1 beta 2 to 1.1 RC1
  • Has patch set to No
#3

Updated by Gerrit Code Review about 9 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/12211

#4

Updated by Gerrit Code Review about 9 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/12211

#5

Updated by Francois Suter about 9 years ago

Michel, I don't know if this will help in your case, but I had the same error message and the mistake, in my case, was a inverted usage of OneToMany/ManyToOne annotation.

#6

Updated by Gerrit Code Review about 9 years ago

Patch set 1 for branch FLOW3-1.1 has been pushed to the review server.
It is available at http://review.typo3.org/12219

#7

Updated by Karsten Dambekalns about 9 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
#8

Updated by Karsten Dambekalns about 9 years ago

  • Target version changed from 1.1 RC1 to 1.1 beta 3

Also available in: Atom PDF