Hi Asanka, I think the first option is better. Having a property like deletable is easy to implement and it is safer than giving users direct access to appfactory.xml .
+1 for having a property called DELETABLE. Thanks On Mon, May 6, 2013 at 8:20 PM, Asanka Dissanayake <asan...@wso2.com> wrote: > Hi All, > > In App Factory application roles are defined in the appfactory.xml. > According to the present situation there are following roles defined. > -Application Owner > -Developer > -QA > -DevOps > > Each role has different permissions. From these roles Application Owner is > very important. > Application owner *MUST* not be able to delete. (ATM if the application > owner is deleted then the application becomes inaccessible ). > > To avoid deleting the appowner ,now delete button is hidden in the UI. to > accomplish this task appOwner is hard coded and compared. If user changed > the role name of the app owner in the appfactory.xml, this does not work. > > to avoid this there may be following options. > > -declare a property called DELETABLE > -or else we can give a UI to edit the content of the appfactory.xml and > hide certain things we want such as app owner etc.. (If we provide this we > should not allow user to open appfactory.xml directly) > > > > > > -- > > *Asanka Dissanayake > Software Engineer* > *WSO2 Inc. - lean . enterprise . middleware | wso2.com* > * > email: asan...@wso2.com <ruch...@wso2.com>, blog: > cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com mobile: +94 71 > 8373821* > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Gayan Dhanushka Software Engineer WSO2 Inc. http://wso2.com Mobile : 0716662327
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
