Re: Inheritance hierarchies

Nathan McEachen escreveu:
> I am working on a project using AspectJ and I am the only developer 
> familiar with aspects.  I also have tried to write aspects that add only 
> orthogonal state and behavior.  Otherwise, I feel the complexity 
> increases dramatically.  The other developers understand AOP only in 
> concept.  They understand that the weaver introduces additional code 
> into their classes, but are not familiar enough with AspectJ to look at 
> my pointcuts and advice to understand the behavior that my aspects 
> implement.  Consequently, when unit testing exposes a bug in one of 
> their classes, they are quick to assume that my "rouge" and "intrusive" 
> aspects may be the culprit. Even though 99% of the time my aspects were 
> not responsible for such bugs, aspects continue to be the number 1 
> suspect.  
>   
In some cases the kind of functionality implemented by the aspects (eg: 
logging, security, etc) can be toggled off from the application and it 
still will work. I haven't been in contact with unit testing frameworks 
for a while, but maybe it there a way to do the unit testing in 2 
rounds, one without aspects and one with. Most business class logic 
should be fairly easy testable without aspects enabled which would point 
the real issue at hand.

Solerman

_______________________________________________
discuss mailing list    -    [email protected]

To unsubscribe and change options, go to:
http://aosd.net/mailman/listinfo/discuss_aosd.net

Check out the AOSD.net Wiki: http://aosd.net/wiki