I had a brief look at the code and saw that there is a different deployer for CARs (which is not an Axis2 deployer). The problem with such an approach is, when we have large scale deployments with many tenants, and when we cannot afford to create a new thread for each tenant CAR deployer. We have to have a single deployment thread. Even with a single deployment thread per tenant, we have faced resource constraint issues in the cloud deployment.
Azeez On Sun, Jun 20, 2010 at 12:08 PM, Isuru Suriarachchi <[email protected]> wrote: > Hi all, > > Now I've finished the application deployment engine and it seems to be > working fine :). But we have to address the following P2 related issues as > I've already mentioned in other threads. > > * Having to restart the server to deploy a cApp > * Problem with upgrading an existing cApp > > Except for the deployment engine, I've finished Axis2, Registry and Synapse > artifact handlers which deploy/undeploy relevant artifacts. In addition to > that, we have the UI components for Axis2 and Synapse artifacts which can be > used to manage artifacts through the UI. But I couldn't test the Synpase > artifact deploymet due to ESB startup issue. > > So now the most important part is almost done and adding support for a new > artifact type (Ex : dataservice, gadget) can be done easily. > > Thanks, > ~Isuru > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Afkham Azeez Senior Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; http://wso2.com, Lean . Enterprise . Middleware Member; Apache Software Foundation; http://www.apache.org/ email: [email protected] cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
