Remove code smell with AOP

re: Remove code smell with AOP

Tuna Toksoz — Sat, 16 Feb 2008 15:49:07 GMT

A useful example would be the Transaction facility of Castle Framework.

You decorate your method with [Transaction] and everything in this method happens in a transaction.

re: Remove code smell with AOP

Amrish — Wed, 16 Jan 2008 05:57:33 GMT

Hey this is nice article and good efforts by you. But we will appreciate if you can provide us with the small live example with implementation, so that we can get a clear view about AOP. We are waiting for your reply with example implementation.

Thanks in Advance

re: Remove code smell with AOP

Roger Alsing — Fri, 11 Jan 2008 09:49:17 GMT

@PBZ

The code that Fredrik have in his example is almost 100% compatible with our framework NAspect.

But our interceptors are called IAroundInterceptor instead of MethodInterceptor.

That, and the methods that should be intercepted needs to be virtual.

So you could take a look at NAspect , www.puzzleframework.com

There are samples that does pretty much what Fredrik describes there.

Does AOP smell or not?

Does AOP smell or not? — Mon, 10 Dec 2007 13:49:21 GMT

Pingback from Does AOP smell or not?

Interesting Finds: November 29, 2007

Jason Haley — Thu, 29 Nov 2007 14:54:03 GMT

re: Remove code smell with AOP

PBZ — Thu, 29 Nov 2007 12:49:36 GMT

OK, that "pseudo code" code example is a start. Can we see a simple, real life, example of: this is how you'd normally do it, and this is how you do it with AOP? Every time I try to read about AOP I'm thrown into this massive never-ending novel reading. I need something quick and dirty to show me why it's so great. If you can convince me that it is then I'll spend the time to read the novel as well...