[Flow] When an Entity extends a non-entity

[Christian Loock]

Hi again,

this is starting to get really frustrating. Every now and then when i 
randomly edit a file, the notice pops again and breaks my project. 
Clearly some cacheing issue. Every time I need to remove my package and 
install it again with composer, which is quite obnoxious during 
development. I set all file permission with the setFilePermission 
command from flow. Still no good. I'm using Flow 2.1 stable.


On 24.04.2014 08:20, Christian Loock wrote:
> Thanks for the Example!
>
> As it seems, it wasn't related to the entity <> no entity thing at 
> all. I reinstalled the Surf Package with composer and now it works. 
> Seems like some sort of cache in the reflectionservice was corrupt.
>
> Cheers
>
>
> On 23.04.2014 17:05, Carsten Bleicker wrote:
>> Example Traits: https://gist.github.com/pumatertion/1d4f458c4493a77dbbf7
>> Hope it helps.
>> In my case it works. And the AbstractDecimal isnt also an Entity.
>>
>>
>> Am 23.04.2014 um 16:47 schrieb Christian Loock <chl at vkf-renzel.de>:
>>
>>> Could you ellaborate on this? I never used traits and am having a 
>>> hard time following here right now. Sorry :(
>>>
>>> On 23.04.2014 16:45, Carsten Bleicker wrote:
>>>> 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
>>>>
>>>> _______________________________________________
>>>> Flow mailing list
>>>> Flow at lists.typo3.org
>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>>> -- 
>>> 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
>>
>>
>> _______________________________________________
>> Flow mailing list
>> Flow at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>

-- 
Christian Loock
Web Developer
Renzel Agentur
www.renzel-agentur.de