A new improvement is added in handling the deployment of faulty Carbon Application, addressing the issue of https://wso2.org/jira/browse/WSAS-1071. When a erroneous Carbon Application is deployed, currently it does not inform user about failure of deploying faulty CApp. Thus a new functionality is added to capture faulty Carbon Applications while deploying, to display the CApp and the fault reason in UI, and to remove those faulty Carbon Applications. Currently, a failure in Carbon Application Deployment can be identified, captured, handled and indicated to the user in the below mentioned scenarios.
- Missing artifact.xml in .car file - Faulty artifact.xml file in .car file - Error occurred while copying Carbon Application. - Missing artifact file in .car file - Error occurred while extracting Carbon Application. - Error in artifact file name But it has to be improved to capture the failures in artifact deployments. Because, the Artifacts Deployment is asynchronous with Carbon Application Deployment. Thus more improvements have to be added to handle those artifacts deployment failures as well. Thank you.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
