http://veerasundar.com/blog/2009/04/the-aspect-oriented-way-of-programming/ Java / Web developer working at PayPal, India. Wed, 08 Sep 2010 07:07:15 +0000 hourly 1 http://wordpress.org/?v=3.0.1 http://veerasundar.com/blog/2009/04/the-aspect-oriented-way-of-programming/comment-page-1/#comment-2193 Raghu Fri, 09 Oct 2009 10:38:46 +0000 http://veerasundar.com/blog/?p=376#comment-2193 Hi veera. Nice article ! But as per my understanding, advice is specifying where the aspect(custom functionality like logging etc) needs to be executed with respect to the join point and there are three types in this viz before, after and around Hi veera. Nice article ! But as per my understanding, advice is specifying where the aspect(custom functionality like logging etc) needs to be executed with respect to the join point and there are three types in this viz before, after and around

]]> http://veerasundar.com/blog/2009/04/the-aspect-oriented-way-of-programming/comment-page-1/#comment-260 Binil Thomas Wed, 13 May 2009 02:44:58 +0000 http://veerasundar.com/blog/?p=376#comment-260 JoinPoint, I think, is some interesting occurrence in the execution of the program. Some code calling a method of an object, some method starting its execution, some exception being thrown, an instance of some class being constructed are all joinpoints. A pointcut is a language construct which picks out one or more joinpoints for advising. Each AOP language has its own syntax for expressing pointcuts. AOP, in general, is beyond interception - although interception provides most of the useful things. See this old TSS thread for arguments on this theme from 2003: http://www.theserverside.com/news/thread.tss?thread_id=17324 Logging is most commonly used example to explain AOP, but it, IMO, is cheesy. Adrian Colyer gives a nice explanation here: http://www.jroller.com/colyer/entry/the_ted_neward_challenge_aop . Please see this interesting paper too: http://citeseer.ist.psu.edu/old/698694.html JoinPoint, I think, is some interesting occurrence in the execution of the program. Some code calling a method of an object, some method starting its execution, some exception being thrown, an instance of some class being constructed are all joinpoints.
A pointcut is a language construct which picks out one or more joinpoints for advising. Each AOP language has its own syntax for expressing pointcuts.
AOP, in general, is beyond interception – although interception provides most of the useful things. See this old TSS thread for arguments on this theme from 2003: http://www.theserverside.com/news/thread.tss?thread_id=17324
Logging is most commonly used example to explain AOP, but it, IMO, is cheesy. Adrian Colyer gives a nice explanation here: http://www.jroller.com/colyer/entry/the_ted_neward_challenge_aop . Please see this interesting paper too: http://citeseer.ist.psu.edu/old/698694.html

]]>