grubbelWeblog of Jonas Bonér [jonas AT codehaus DOT org]AspectWerkz has moved to codehaus.org- May 13, 2003 The move to codehaus.org is now completed. The new URL is aspectwerkz.codehaus.org.http://blogs.codehaus.org/people/jboner/archives/000018_aspectwerkz_has_moved_to_codehauso... AspectWerkz 0.5 has been released- May 12, 2003 The AspectWerkz 0.5 release is a huge improvement compared to previous versions. Apart from many bug fixes it is also packed with new features. You can download the new release from the releases page. New features: Caller side pointcuts. I.e. the possibility to advise a method invocation (caller side) apart from method execution (callee side). .http://blogs.codehaus.org/people/jboner/archives/000016_aspectwerkz_05_has_been_released.h... AOP standardization process started- May 10, 2003 Renaud Pawlak, the creator of JAC has started up a project called AOPI, which has the goal of specifying a common set of components for aspect-oriented systems. From the homepage: AOPI are a standard specification of a set of useful or mandatory componants for aspect-oriented systems. The idea is to have a common set of abstract components specifications, distributed under a Public Domain licence, that will help all the projets to communicate and reuse components coming from other...http://blogs.codehaus.org/people/jboner/archives/000011_aop_standardization_process_starte... AOP in practice: Transparent persistence for POJOs- May 10, 2003 Using the new techniques of AOP and the AspectWerkz framework there is actually pretty easy to implement transparent persistence for Plain Old Java Objects (POJOs). This example has been implemented using JISP as persistence engine and can be checked out along with the AspectWerkz distribution from the CVS. (Please note that the documentation is not all up to date). First we have to write a PostAdvice similar to this one: public final class DirtyFieldCheckAdvice extends PostAdvice .http://blogs.codehaus.org/people/jboner/archives/000010_aop_in_practice_transparent_persis... Cedric's AOP challange: a solution using caller pointcuts and decoupled advices.- May 10, 2003 Last night I implemented caller pointcuts for AspectWerkz. I just had to, since they have been haunting me since I read Cedric's little AOP challange. So for what it is worth, here is my way of implementing Cedric's caching problem using AspectWerkz and caller pointcuts. I'll start with the cache advice. The CachingAdvice caches the result and if the cache is used it reports it to the CacheStatistics instance: public class CachingAdvice extends MethodAdvice protected Map...http://blogs.codehaus.org/people/jboner/archives/000009_cedrics_aop_challange_a_solution_u... |