[Flow] When an Entity extends a non-entity

[Carsten Bleicker]

Stumbled about something like that.
Think i was ending up in using traits to define the properties and put them into the entity model wich extends a non entity model.


Am 23.04.2014 um 16:37 schrieb Christian Loock <chl at vkf-renzel.de>:

> Hello,
> 
> I am currently working on a little web Interface for my Surf Deployment to Configure Nodes. I created my Own Node Entity that extends \TYPO3\Surf\Domain\Model\Node. The generation of migrations and creating database structure all works, all members are taken from the parent class and created in the database. However, now that I try to use the Model in a controller to actually work with it, i get the following notice:
> 
> Notice: Undefined index: TYPO3\Surf\Domain\Model\Node in
> /xxx/Packages/Framework/TYPO3.Flow/Classes/TYPO3/Flow/Reflection/ReflectionService.php
>  line 1613
> 
> The error happens when the Reflection Service does a check on the Parent class of the object, but the parent class apparently is not known to the ReflectionService. The class however exists and should be known to Flow, since is aware of the Surf Package. It is weird and I feel like it might be related to the fact that the parent class is not an Entity, but my class is. Did i find a bug here or am I on the wrong train of thought in the problem might be a whole different one?
> 
> Does anybody have any experience with such cases and could help out?
> 
> Thanks in advance and cheers!
> 
> -- 
> Christian Loock
> Web Developer
> Renzel Agentur
> www.renzel-agentur.de
> 
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow