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 - TYPO3.Flow - TYPO3 Forge

TYPO3 Flow Base Distribution TYPO3.Eel TYPO3.Flow TYPO3.Fluid TYPO3.Kickstart TYPO3.Welcome Packages Applications

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

Status:

Resolved

Start date:

2012-05-28

Priority:

Must have

Due date:

Assigned To:

Karsten Dambekalns

% Done:

100%

Category:

Persistence

Target version:

TYPO3 Flow Base Distribution - 1.1 beta 3

PHP Version:

Complexity:

Has patch:

Affected Flow version:

Git 1.1

Description

title says all

Related issues

Associated revisions

Revision a88b400c
Added by Karsten Dambekalns about 3 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
Added by Karsten Dambekalns about 3 years ago

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

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

History

#1 Updated by Karsten Dambekalns about 3 years ago

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

#2 Updated by Karsten Dambekalns about 3 years ago

Category set to Persistence
Status changed from New to Accepted
Assigned To set to Karsten Dambekalns
Target version changed from 1.1 beta 2 to 1.1 RC1
Has patch set to No
Affected Flow version set to Git 1.1

#3 Updated by Gerrit Code Review about 3 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 3 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 3 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.