Another enhancement to this could be the ability to configure "default" pre-processing ActionProcessors for specific listener classes - these actions get inserted at the start of the configured pipeline. This could be used e.g. for message normalisation (a hot topic at the moment ;-) ). So for e.g. the JMSListener you could have a default action processor that "normalises" the based on a combo of JMS and your chosen normalisation strategy. So the "Actions" config might look something like: <Actions> | <!-- Action configs .... --> | <!-- ProcessorAliases configs .... --> | | <DefaultActions listener="listenerA" actions="action-list..." /> | <DefaultActions listener="listenerB" actions="action-list..." /> | </Actions> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971312#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...