On Mon, Mar 4, 2013 at 1:34 PM, Tharindu Mathew <[email protected]> wrote:
> Overwriting the existing is the standard behavior in web apps. This makes > deployment and testing easy as well. I think it should be the same for > jaggery apps. So, this behavior should be changed. > Jaggery deployment follows a different model where the changes to the app gets reflected on the fly, which is different form the normal axis2 hot-deployment concept (unDeploy first and deploy again). Also if i remember correctly, that was the requirement as you can just edit the jag files or add new jag files on the fly, to the jaggery app (without the need to redeploy them every time) and the changes will get reflected instantly. For other app types, when deploying a new app with the same name, first it will undeploy the existing one and the deploy the new one, which is the normal axis2 deployment model. Thanks, Kishanthan. > > On Mon, Mar 4, 2013 at 12:57 PM, Supun Malinga <[email protected]> wrote: > >> Hi, >> >> +1 For allowing the user to upload after confirmation. As for the current >> implementation user cannot upload a jaggery app with the same name twice. >> But saying that, all other artifact deployment happens blindly copying >> over the existing artifact. We may need to take a decision regarding that >> as well. >> >> thanks, >> >> On Mon, Mar 4, 2013 at 12:47 PM, Nuwan Bandara <[email protected]> wrote: >> >>> >>> >>> >>> On Mon, Mar 4, 2013 at 12:16 PM, Ajanthan Balachandran < >>> [email protected]> wrote: >>> >>>> Hi All, >>>> $subject fails with back end log "Jaggery app with the same name >>>> already exists".But in the case of Web App it first undeploy the >>>> previous one and deploy the new one.Which is the correct behavior ? >>>> >>> >>> I think Jaggery behaves correctly. Imagine, user X creates an app called >>> Foo and uses it, and later User Y logs in and add a new app called foo, If >>> we silently replace the app, then its a problem. we give a warning. If its >>> a conscious decision, he can remove the old foo first and deploy the new >>> one. >>> >>> Regards, >>> /Nuwan >>> >>> >>>> Thanks >>>> -- >>>> ajanthan >>>> -- >>>> Ajanthan Balachandiran >>>> Software Engineer; WSO2, Inc.; http://wso2.com/ >>>> email: [email protected]; cell: +94775581497 >>>> blog: http://bkayts.blogspot.com/ >>>> >>>> Lean . Enterprise . Middleware >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>> >>> >>> >>> -- >>> *Thanks & Regards, >>> >>> Nuwan Bandara >>> Associate Technical Lead & Member, MC, Development Technologies >>> WSO2 Inc. - lean . enterprise . middleware | http://wso2.com >>> blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 >>> 9629 >>> * >>> <http://www.nuwanbando.com/> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Supun Malinga, >> >> Software Engineer, >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> email - [email protected] <[email protected]> >> mobile - 071 56 91 321 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Regards, > > Tharindu Mathew > > Associate Technical Lead, WSO2 BAM > Member - Data Mgmt. Committee > > blog: http://tharindumathew.com/ > M: +94777759908 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
