"richard.opalka(a)jboss.com" wrote : | ad1) Put all deployers to the same collection (not list per stage like current impl) | ad2) on deployers chain retrieval | * check whether sorting needs to be done (yes if deployers were added/removed to/from the chain from last getDeployersList() method call) | * sort all deployers if change is detected only | ad3) Return all deployers belonging to requested deployers chain (getDeployersList() method call) from sorted list of deployers | Nah, changing stages automagically is something you don't wanna do, even though the order might appear to be wrong. I would expect the stage to be set on purpose. e.g. POST_CL, since I need ClassLoader to be present, hence I don't wanna that my order changes based on someone else's illegal input/output "richard.opalka(a)jboss.com" wrote : | NOTE: Sorting algorithm have to take deployment stages, inputs, outputs and relative order into account. Current algorithm based on comparing two deployers doesn't include all possible usecases and it ignores inputs and stages. | We don't ignore inputs --> inputs == Dots::head in Dominoes View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240027#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...