Bug #27285
Exception with /** @MappedSuperclass */
| Status: | Resolved | Start date: | 2011-06-07 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Persistence | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0.3 | |||
| PHP Version: | Complexity: | |||
| Has patch: | No | Affected Flow version: | FLOW3 1.0.0 |
Description
If you have a mapped superclass in Domain/Model folder you will have an exception unless you mark the class with @entity
Doctrine2 Examples http://www.doctrine-project.org/docs/orm/2.0/en/reference/inheritance-mapping.html dont mark this kind of clasess as @entity
Not sure if it's better to mark as entity, may be yes, but it doesnt seem necessary in Doctrine2. All works ok and no new table is created in DB after tag as @entity
#1295973082 No class schema found for "F3\Sifpe\Domain\Model\Apunte"
RuntimeException thrown in file
/var/www/html/FLOW3/Data/Temporary/Development/Cache/Code/FLOW3_Object_Classes/F3_FLOW3_Persistence_Doctrine_Mapping_Driver_Flow3AnnotationDriver_Original.php in line 89.
Related issues
Associated revisions
[BUGFIX] Hint at possible exception cause
When using @MappedSuperclass without @Entity an exception is thrown.
Since FLOW3 needs the @Entity annotation even with a mapped superclass,
this change adds a hint to the exception message.
Change-Id: I0cfe579bc54afc473162e21d596d70408d82bb1d
Fixes: #27285
Releases: 1.0, 1.1
[BUGFIX] Hint at possible exception cause
When using @MappedSuperclass without @Entity an exception is thrown.
Since FLOW3 needs the @Entity annotation even with a mapped superclass,
this change adds a hint to the exception message.
Change-Id: I04cf950f79519daedb3f84e8b2d9f27361b46516
Fixes: #27285
Releases: 1.0, 1.1
History
#1 Updated by Karsten Dambekalns about 4 years ago
- Category set to Persistence
- Status changed from New to Accepted
- Assigned To set to Karsten Dambekalns
#2 Updated by Karsten Dambekalns almost 4 years ago
- Affected Flow version set to FLOW3 1.0.0
#3 Updated by Karsten Dambekalns over 3 years ago
- Target version set to 1.0.3
- Has patch set to No
Yes, in FLOW3 all entities must be marked as such. The entity declaration has more significance than only for persistence, thus simply using MappedSuperclass as a "shortcut" to Entity is not an option.
But I will change the exception message to contain a hint.
#4 Updated by Gerrit Code Review over 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/7675
#5 Updated by Gerrit Code Review over 3 years ago
Patch set 1 for branch FLOW3-1.0 has been pushed to the review server.
It is available at http://review.typo3.org/7861
#6 Updated by Gerrit Code Review over 3 years ago
Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/7675
#7 Updated by Karsten Dambekalns over 3 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset ad89e84eecd5170b0ce87ac340c1c564acc67983.