As discussed in JBW, we are going to define a new, state of the art Dynamic AOP API for the next JBoss AOP version (after we go GA). I decided to give the initial kick and start this thread. Mainly, I see two options here: improving the existing API or coming up with a brand new API (an adaptation layer to our current API) Improving the existent API would consist mainly of creating more intuitive constructors for AspectDefinition and AdviceBinding (such as removing cflow, and allowing definition of cflow using varargs), and adding more methods to AdviceBinding (addAdvice(Class<?> aspectClass, String adviceName)). The advantage of doing so is that we stick with our already existing classes. One of the problems I see with extending the existent API is that we would still force the user to register secondary stuff in the AspectManager, such as cflow and aspect definitions. Besides, with a new API, we would be free to make dynamic AOP more straighforward, and it could be simpler for the end user to use it if he doesn't have to use AspectManager (I mean, there are so many methods in AspectManager, everything being mixed up in a single class can make users confused). So, Kabir, what do you have in mind for this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166298#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...