Hi All, On Fri, Sep 21, 2012 at 8:18 PM, Supun Malinga <[email protected]> wrote:
> > > On Fri, Sep 21, 2012 at 7:41 PM, Kishanthan Thangarajah < > [email protected]> wrote: > >> >> >> On Fri, Sep 21, 2012 at 11:18 AM, Thilini Shanika <[email protected]>wrote: >> >>> 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 >>> >>> >> +1. This is a useful improvement, which allows to correct the faulty >> C-App and deploy the correct one. >> > > +1 > +1 > > >> >>> >>> But it has to be improved to capture the failures in >>> artifact deployments. Because, the Artifacts Deployment is asynchronous >>> with Carbon Application Deployment. >>> >> >> This is because, C-App deployment only deals with copying artifacts >> (apart from registry resources) to the relevant hot update directories. The >> actual deployment of those artifacts are handled by those relevant >> deployers. So currently C-App deployment has no control on these individual >> artifacts deployment. >> > > yes, but we do show the C-App related artifacts under the relevant C-App. > So we should be able to track down the faulty ones as well. > True. We can show the fault artifacts but tracking down the error would be difficult since we have to write a error capture logic in each and every individual artifact as well as a Call Back Handler to call the C-App deployer to report the status back. Thanks and Regards, Harshana > > Will apply the patches given. > > thanks, > >> >> >> Thus more improvements have to be added to handle those artifacts >>> deployment failures as well. >>> >>> Thank you. >>> >> >> >> >> -- >> *Kishanthan Thangarajah* >> Software Engineer, >> Development Technologies Team, >> WSO2, Inc. >> lean.enterprise.middleware >> >> Mobile - +94773426635 >> Blog - *http://kishanthan.wordpress.com* >> Twitter - *http://twitter.com/kishanthan* >> >> > > > -- > Supun Malinga, > > Software Engineer, > WSO2 Inc. > http://wso2.com > http://wso2.org > email - [email protected] <[email protected]> > mobile - 071 56 91 321 > > -- Harshana Martin Senior Software Engineer Member, Management Committee - Development Technologies WSO2 Inc. : http://wso2.com ; http://wso2.org Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
