On Wed, Nov 11, 2015 at 3:04 PM, Inosh Goonewardena <[email protected]> wrote:
> Hi, > > On Wed, Nov 11, 2015 at 2:52 PM, Nirmal Fernando <[email protected]> wrote: > >> >> >> On Wed, Nov 11, 2015 at 2:32 PM, Sachith Withana <[email protected]> >> wrote: >> >>> The problem occurs when deploying CApps. >>> >>> If we try to deploy a CApp which contains the gadget "x" ( without >>> knowing that there is another gadget already there with the same name), >>> >> >> Within a single tenant this is not a valid reason IMO, cause Capp >> developer can see the existing gadgets. >> > > If we are not going to support using same gadget name in two different > CApps, then we should then this as a limitation. IMO, it is completely ok > for user to use same name for gadgets in two different CApps. > My initial question is still hold. "Under a single tenant, what's the usage of having two X named gadgets? " > >> >>> that gadget would be overridden with the new one. >>> >> >>> On Wed, Nov 11, 2015 at 2:25 PM, Nirmal Fernando <[email protected]> >>> wrote: >>> >>>> Under a single tenant, what's the usage of having two X named gadgets? >>>> >>>> On Wed, Nov 11, 2015 at 1:56 PM, Sachith Withana <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> Currently in the CApp deployment, the gadgets and the layout are >>>>> copied to gadget or layout directories under the tenant ID. >>>>> >>>>> With the current implementation, if there's already a gadget deployed >>>>> called "x", and another CApp tries to deploy its own gadget called "x", >>>>> the >>>>> previous gadget gets overridden since all the gadgets are copied to the >>>>> same gadget folder for the same tenant. >>>>> >>>>> IMO this should be prevented. >>>>> >>>>> If we prefix the gadget folder with the respective CApp name, since >>>>> the gadget name taken from a property file inside the gadget folder, there >>>>> will be multiple gadgets with the same name appearing in the dashboard. >>>>> >>>>> Any thoughts on how we could solve this issue? >>>>> >>>>> >>>>> -- >>>>> Sachith Withana >>>>> Software Engineer; WSO2 Inc.; http://wso2.com >>>>> E-mail: sachith AT wso2.com >>>>> M: +94715518127 >>>>> Linked-In: <http://goog_416592669> >>>>> https://lk.linkedin.com/in/sachithwithana >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Thanks & regards, >>>> Nirmal >>>> >>>> Team Lead - WSO2 Machine Learner >>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc. >>>> Mobile: +94715779733 >>>> Blog: http://nirmalfdo.blogspot.com/ >>>> >>>> >>>> >>> >>> >>> -- >>> Sachith Withana >>> Software Engineer; WSO2 Inc.; http://wso2.com >>> E-mail: sachith AT wso2.com >>> M: +94715518127 >>> Linked-In: <http://goog_416592669> >>> https://lk.linkedin.com/in/sachithwithana >>> >> >> >> >> -- >> >> Thanks & regards, >> Nirmal >> >> Team Lead - WSO2 Machine Learner >> Associate Technical Lead - Data Technologies Team, WSO2 Inc. >> Mobile: +94715779733 >> Blog: http://nirmalfdo.blogspot.com/ >> >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Thanks & Regards, > > Inosh Goonewardena > Associate Technical Lead- WSO2 Inc. > Mobile: +94779966317 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Thanks & regards, Nirmal Team Lead - WSO2 Machine Learner Associate Technical Lead - Data Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
