I added a state enum to the DeploymentInfo and this is being populated by the MainDeployer. In going through this as part of working on some deployment bugs one obvious problem is that the state of the DeploymentInfo is largely ignored. This leads to the coarse entry points of the MainDeployer trying to walk through an implicit state machine based on complex logic in its various init, created, start, etc. methods. This needs to be flipped so that the state of the DeploymentInfo drives what the MainDeployer is doing so that a deployment can be continued at any point its state. This will simplify that tracking of problems, identification of deployment cycles, and should also allow for minimal work in completing failed or incomplete deployments. This is something Julien Viet had suggested as part of some patches he has been working on.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
