"ben.wang(a)jboss.com" wrote : So what we need to do is during the copying of the JBC library from 3d party dir to build, we need to do an "aopc" on the jar. | | But in this way, Kabir, I will need to unjar pojocache.jar first and then jar it again after instrumentation, is it correct? | Yes "ben.wang(a)jboss.com" wrote : | One other issue is for future upgrade. User can not simply drop the jar from the JBC released version. | Hence the "install" script I mentioned. I think jboss messaging does this as well. "ben.wang(a)jboss.com" wrote : | Now why can't JBoss Aop try to maintain some binary compatability between releases? | Now that this has become a requirement, we will attempt to do this. I have always seen the woven code as an internal implementation detail, and so have not really thought about this part before. Now that we have run into a real need for this we will attempt to keep this in sync between minor versions. However, before we go final with 2.0.0.GA we *might* still need to make adjustments to what is being woven in. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986623#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...