"kabir" wrote : | I've vaguely started thinking about this in the back of my mind, and am curious about how you see a few of the initial concepts. | | In the current linear one, install/uninstall = move to next/previous state. | | In the tree-based one, there will be more than one state to "install" to. Something needs to decide that. How will the decision be made, and who will make it, about what state to move to? | | Going "back" will one always transition to the fromState? Or can there be several of these as well? This question feels weird, but I was thinking of circular states such as | "Does Not Exist" <-> "method ready" | ^-------------> passive <-----^ | It would still be sort of linear, meaning we wouldn't have to change too much. At that time I was thinking about having some sub-linear path in the ControllerContext. And you would only change that path once you needed a different state "route". Afair this would work, you would only need some additional checks. e.g. confirming that the path you provided is legal e.g.2 checking if the state you wanna transfer exists on that path ... And instead of asking the Controller to provide the state model, you would ask the ControllerContext for his current linear path. HTH View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224583#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...