[TYPO3-50-general] Accessing the AspectContainer / AOPBrowser

[Michael Feinbier]

Hi Malte,

Malte Jansen schrieb:
> Hi Michael,
> 
> I'm not into the AOP-part yet,
> 
> but if I understand you correctly, you want some overview about, where 
> aspect affects an other class etc.

Yes, exactly :)

> 
> Why don't you analyse the classes? It's pretty easy to search for the 
> class and read out the doccomment... You can check out the FLOW3CGL and 
> PHPCodeSniffer Packages...
> Perhaps it's easier to collect the classes and aspects directly from the 
> Classes-folder and interprete them afterwards.
> 

Yes, of course that would work. But I thought I didn`t have to reinvent 
the wheel. All this collection, parsing, proxiing is already done by the 
AOP-Framework, so why not using that?
Furthermore i want to present the registrered advices and pointcuts 
exactly as the aop-framework will use. Maybe my recoding of the advice 
collecting is in somethings different from that of the aop-framework. So 
the Browser would show different results.

But I think I will do so, because this seems the only way for now. With 
pretty good unit-tests i think i will be able to get identical results 
to the aop-framework.

I will have a look on FLOW3CGL as well, thanks for that hint :-)

> (The DocComment-Checks will follow until the weekend.)
> 
> 
> Cheers,
> 
> Malte
> 

Micha

> PS: Feel free to add the bugs to the corresponding project on 
> forge.typo3.org ;)
> 
> Michael Feinbier schrieb:
>> Hi there,
>>
>> for some time now i am working on the pratical part of my bachelor 
>> thesis, which consists of implementing some kind of aop-browser.
>>
>> My idea to browse through aspects, advices and so on was to use the 
>> var $aspectContainers from T3_FLOW3_AOP_Framework which holds all 
>> Advices if i debug that correctly.
>> Because the $aspectContainers is protected, I cannot acces that 
>> through my Browser component, so i decided to introduce a new Method 
>> getAspectContainers as described in the documentation.
>>
>> I wrote a new Interface declaring the getAspectContainers method and 
>> an aspect introducing the new interface and around-advising the newly 
>> introduced method.
>>
>> Well, then i realised that this is a chicken or the egg dilemma. I 
>> think it is not possible to advice methods of the AOP-Framework 
>> itself, right?  Because the Framework has to be initialized to make 
>> use of the paradigm.
>>
>> So is there a neat possibility to access $aspectContainers from the 
>> T3_FLOW3_AOP_Framework component without changing the source of that 
>> component?
>>
>> Maybe there is a way to get that injected from the component-manager?
>>
>> Thanks for hints and advises..
>>
>> PS: found some small bugs in code-listings of the documentation. 
>> should i open tasks on forge for that?
>>


-- 
kind regards from Bielefeld

Michael

Error 404: The city you are looking for doesn't exist.
http://www.denkweite.de | http://www.feinbier.net