[jboss-dev-forums] [Design of POJO Server] - Re: Updating docs

[adrian@jboss.org]

They express an intention to implement 2 phase deployment
and atomic redeployment.

new.prepareDeploy() // take the new deployment to the ready stage
old.prepareUndeploy() // get ready to undeploy
handoff(new, old); // handover control
new.commitDeploy(); // you are now in control
old.commitUndeploy(); // you are out of here

I doubt the final api will be this simple since it will have to deal
with mutliple deployers on multiple aspects of the deployment. :-)

For now, the AbstractSimpleDeployer is a better api
with its deploy()/undeploy()

In fact, I'm aiming for an api where the deployers don't
really deal with the lifecycle directly and instead provide
metadata on which parts of the deployment they want
to do work on and "when".

e.g.
SARDeployer
I create a ServiceDeployment and LoaderRepositoryConfig from -service.xml 

ServiceDeploymentDeployer
I split a ServiceDeployment into its component ServiceMetaData

ServiceClassLoaderDeployer
I create classloaders from LoaderRepositoryConfig

ServiceDeployer
I'm the real deployer of ServiceMetaData

etc.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972610#3972610

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972610