[aosd-discuss] Are frameworks crosscutting?

[Dean Wampler]

I think this is the central reason why frameworks have not been as 
successful as people expected them to be, with a few exceptions (mostly 
GUI toolkits).  They must balance wide coverage to appeal to a broad 
audience, yet that coverage tends to make them bloated and inappropriate 
for most users who need only "pieces" of functionality.

I do believe that AOP offers a promising solution, by decoupling the 
explicit dependencies so that more pieces can be adopted "al a carte" 
when appropriate, yet nontrivial applications can be composed using 
aspects to coordinate the pieces and implement new functionality. Those 
pieces can come from a variety of providers, too.

dean
-- 
Dean Wampler, Ph.D.
dean at aspectprogramming.com
http://www.aspectprogramming.com
http://www.contract4j.org
I want my tombstone to say:
    Unknown Application Error in Dean Wampler.exe.
    Application Terminated.
    [Okay]    [Cancel]


Paul Soule wrote:
> Hi,
> 
> If we have an OO framework, that framework's code is contained in all 
> classes that inherit from, or contain, that framework. When used, the 
> framework's code will crosscut a system's functionality because it will 
> be contained in any class that uses the framework.
> 
> Is it therefore true to say that all concerns contained in a framework 
> are inherently crosscutting in nature because the concerns will, via 
> inheritance or containment, be scattered through an application that 
> uses the framework?
> 
> Thanks,
> Paul
> 
> 
> __________________________________________________
> AOSD Discuss mailing list    -    discuss at aosd.net
> To unsubscribe go to http://aosd.net