If you want to intercept onMessage() only, you're probably better off creating a custom AOP domain for message driven beans (see deploy/ejb3-interceptors-aop.xml for examples of how to do this) and to use the @AspectDomain annotation on your message driven beans where you want this behaviour. This will avoid the need for weaving your classes. There should be some examples on how to do this in the ejb 3 documentation or user forum. Regarding your question, it "should work" for onMessage(), but I am not sure how ejb3 interacts with woven classes, and since EJB3 uses AOP to configure itself, there might be some problem with aspects on EJB 3 business methods. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251636#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...