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 7 years ago. Updated over 7 years ago.

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

100%

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 displayed Resolved 2012-03-05

Associated revisions

Revision a88b400c (diff)
Added by Karsten Dambekalns over 7 years ago

[BUGFIX] Inform about possible cause for "No class schema found"

When mapping meta data for Doctrine an error about "No class schema
found for …" could occur. It would not tell in what model the mapping
was taking place, leaving the user to guesswork. This adds output
of the currently examined class to the exception.

Change-Id: I5c617cbc28b02db1e3b7389f963fd1ab50b3cf3b
Fixes: #37547
Releases: 1.1, 1.2

Revision 82e8f439 (diff)
Added by Karsten Dambekalns over 7 years ago

[BUGFIX] Inform about possible cause for "No class schema found"

When mapping meta data for Doctrine an error about "No class schema
found for …" could occur. It would not tell in what model the mapping
was taking place, leaving the user to guesswork. This adds output
of the currently examined class to the exception.

Change-Id: I5c617cbc28b02db1e3b7389f963fd1ab50b3cf3b
Fixes: #37547
Releases: 1.1, 1.2

History

#1 Updated by Karsten Dambekalns over 7 years ago

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

#2 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 changed from 1.1 beta 2 to 1.1 RC1
  • Has patch set to No

#3 Updated by Gerrit Code Review over 7 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 over 7 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 over 7 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 over 7 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 over 7 years ago

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

#8 Updated by Karsten Dambekalns over 7 years ago

  • Target version changed from 1.1 RC1 to 1.1 beta 3

Also available in: Atom PDF