I think semantically what you're after is a different approach - rather than trying to install everything in parallel, what is needed is a sort of lifecycle task abstraction. The logic would be something to the effect of: | task is: | execute lifecycle method; | for each task that depends on me { | remove me as a dependency; | if no remaining dependencies { | submit task to executor; | } | } | In other words, one executor task per controller task. This would allow full concurrency of everything that can be expressed in terms of dependencies, including having different lifecycle methods being executed concurrently etc. Now I have no idea how this fits in to the existing lifecycle code. If at all. :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238045#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...