Hi, On Sat, Aug 21, 2010 at 2:10 PM, Afkham Azeez <[email protected]> wrote:
> There is a better way to fix this. The Carbon webapp gets deployed first, > and the deployment of other webapps follow. So, the WebappDeployer can get > the list of registered sub-contexts (from the HTTPService?), and pass them > down to Tomcat when it tries to deploy a webapp. If there is a clash between > a Carbon sub-context & the context of a new webapp to be deployed, a > deployment exception can be thrown preventing the deployment of the webapp. > If we are deploying a webapp with an already existing *user deployed* webapp in the same context, will it throw an exception? Then, is this webapp get deleted or kept as we do for our faulty services? In that case, if the server is restarted after that, can we guarentee which webapp will register first? thanks, Ruchira
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
