Michael Burman [http://community.jboss.org/people/burmanm] created the discussion "Re: Annotation based Action classes" To view the discussion, visit: http://community.jboss.org/message/576559#576559 -------------------------------------------------------------- Is it by design that these work differently than the old actions? There are two things which don't work: 1. Transactions aren't supported, rollback doesn't happen since BeanContainerAction wraps everything as "ActionProcessingException". The JCA adapter doesn't get RuntimeException, which is needed for the rollback to occur. This works correctly in the ActionProcessingPipeline, which detects the RuntimeException if it's running in transactional mode and throws it. 2. Terminating the action flow doesn't work anymore by setting the message as null. This works with older ActionProcessingPipeline where returning message as null causes the pipeline to die with break;. However, in the BeanContainerAction, if the return value is null the original payload is reset. If these are intentional, they should be documented. I don't know how many hours I spent debugging our software and wondering why on earth things stopped working in certain cases. If these are unintentional, I can create JIRA tickets, and I can even submit possible patches. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/576559#576559] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]