Basically, the ActionProcessor definition seems fundamentally flawed to me in that notification generation (OK and Error) is done seperately from the message processing to which it is inextricably tied. That's what I meant originally when I said that I thought it was "dodgy". The way I see this, saving before/after/whatever objects is not going to fix this properly - the notifications need to be generated in context i.e. in line with the message processing to which they are tied. Doing it any other way is always going to cause trouble for somone. Whether or not this is sorted out for the GA is (I think) a question of how important Notifications are for the GA. I suggested somewhere else that we could implement a notification mechanism by allowing the process method impls add notification objects to the Message. A list of notifications (info, warn, error) could accumulate on the message as it flows through the pipeline, being sent once the pipeline processing is complete (the notification list retrieved from the message via some form of getter). This may need to tie in in some way with the message Fault?? This would also enable an ActionProcessor impl to send multiple notifications from within the context of the processing of a single message. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976924#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...