Previous Parts of the series Part 1 – The basic of interception Part 2 – Selecting Methods to intercept Part 3 – The first interceptor AOP works great if you have clear interfaces where you want to put some standard and shared logic, and a Service Oriented Application falls in this category. A service is [...]
Continue reading about AoP with castle part 4–Adding AoP to service oriented App
Previous Parts of the series Part 1 – The basic of interception Part 2 – Selecting Methods to intercept Usually the very first interceptor you can build with an AOP framework is the “logger Interceptorâ€, because it is simple and useful, especially when you expose some services with WPF. Consider this scenario: you expose some [...]
Continue reading about AOP With castle–Part 3-The first interceptor
Thanks to AOP concept, creating a cache layer that is transparent to the caller is not a big deal. I have a piece of code that in a loop calls this method 1: ClientCompetitor competitor = Repository.ClientCompetitor.GetByCriteria( 2: Query.CreateEq("AssociatedClient", clieid)) 3: .SingleOrDefault(); 4: This is based on a standard implementation of repository and a Specification [...]
I made a session about Aop with castle in a Italian workshop oranized by our association DotNetMarche, and some of the attendee asked me to publish the material in my blog. So I decided to start to publish all material in english language. Introduction If you look at canonical terms of aop you can recognize [...]
