This has been added. I originally modified AbstractController, but found that the callbacks were being "uninstall"ed twice, so it does its own unwinding. I've added some checks to AbstractLifecycleCallbackItem to check if the "install" callback was called for a particular callback, and if not to skip the "uninstall" step for that. One borderline case is the lifecycle callback whose "install" method caused an error, should the callback for that be called or not? I think so, since it might have had partial success. See UnwindLifecycleTestCase for details. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051057#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...