Tom, As a result of your observation yesterday, I have introduced a fix for that problem. The AbstractListener will now keep the 'before action' as well as the 'after action' current object, until the processing pipeline is about to start the next step in the chain. As a consequence of this, the notification methods (and in fact any other methods that we might have in the future invoked after the process(Message) and the end of this action) have now access to both. (before and after action). Thanks. E View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976747#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...