This sounds somewhat like deciding for the user how to use the system. Why not add some flexibility - e.g. as with spring, you could point out the scope of the handler (like singleton). Pool is good for non singleton handlers (like jsf works). About the state in the action handler - we use that to autowire spring dependencies (@Autowire annotation) For now we are using only singleton scope, so that's not a problem (if you don't reload spring container), but what if you want to add some custom scope, let's say @ProcessInstance. Anyways, it's just an example, the idea is, why add some restrictions, where flexibility is wanted. I'm for configurable option, and not globally of course, but for each handler (with sensible default). cvl View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211621#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...