[jboss-dev-forums] [Design of POJO Server] - Re: Hot deploying deployers - deployer chains

"scott.stark(a)jboss.org" wrote : | Second, explain how the tree is used given a DeploymentContext representing an ear with the full contigent of javaee components, and customized aspects like security and logging. | Ignore the deployment context. That is just the current iteration's version of the DeploymentInfo. Basically a big horrible map of metadata and state about the deployment. What we are really dealing with is: * managed objects - either predetermined using our metadata formats or the unparsed xml and annotations * structure - where to look for unparsed metadata and what makes up the classpath * transient state - used during the deployment In the full solution, the management component of the profile service should be able to say something like: "change the pool size of this datasource" and it is the MainDeployer's job to say (based on the meta annotations), I can do that (with the help of the relevant deployer) without going through a redeploy. It can't do that with the current MainDeployer api and DeploymentContext. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972634#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...