Should probably add that this is running JbossESBServer 4.4.
Unfortunately the BeanConfiguredAction was not written to support the processSuccess/processException methods.
As you can see from http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/rosetta/src/org/jboss/soa/esb/listeners/message/BeanConfigActionProcessor.java, it creates a new instance of the bean on every invocation and ans stubs out the other methods.
It is likely to perform poorly given this and, therefore, you would be better using a normal action interface.
Check. I'll pass that on to the rest of my team. Thank you for the information.