New episode from SE-Radio.net: Basic Introduction to AOP (Aspect Oriented Programming)

I want to post the SE-Radio.net Episode 106 about AOP programming and two nice presentations from slideshare.net.

AOP importance is increasing in the past few years, Spring are using it in a widely manner and also OSGi have announced few month ago your Aspect bundle for weaving at run-time (Equinox Aspect). So AOP have a grait impact on present programming and I think that it will have also with future programming.

Equinox Aspect: Example from Martin Lippert

Martin Lippert is a senior consultant and coach at akquinet it-agile GmbH. His main work and research focuses on Agile Software Development, Refactoring, Eclipse-Technology, OSGi, Spring and Aspect-Oriented Programming.

Martin posts, in your blog, a Code Examples from “Aspect Weaving for OSGi” Talk.

The code example is divided in:

• Eclipse Monitor Demo
• Dependency Injection with Spring Dynamic Modules and Equinox Aspects

OSGi and AspectJ into Equinox Aspects

In software engineering, the programming paradigms of aspect-oriented programming (AOP), and aspect-oriented software development (AOSD) attempt to aid programmers in the separation of concerns, specifically cross-cutting concerns, as an advance in modularization. AOP does so using primarily language changes, while AOSD uses a combination of language, environment, and method.

Separation of concerns entails breaking down a program into distinct parts that overlap in functionality as little as possible. All programming methodologies—including procedural programming and object-oriented programming—support some separation and encapsulation of concerns (or any area of interest or focus) into single entities. For example, procedures, packages, classes, and methods all help programmers encapsulate concerns into single entities. But some concerns defy these forms of encapsulation. Software engineers call these crosscutting concerns, because they “cut” across multiple modules in a program.