On Tue, Mar 31, 2015 at 12:13 PM, Nandika Jayawardana <nand...@wso2.com> wrote:
> I prefer to make it a configurable option. Since specification does not > allow creating task with the same name, lets make it the default behavior. > We can give an option from the configuration file to define whether to > create a new task. > Yes, Let's make it configurable. Thanks, Hasitha. > > Regards > Nandika > > On Tue, Mar 31, 2015 at 7:13 AM, Hasitha Aravinda <hasi...@wso2.com> > wrote: > >> Hi, >> >> [Adding Architecture] >> >> According to HT spec we can't have two lean task definition with same >> name. But we provide versioning for HumanTask, So IMO we can apply same >> Task versioning rules for LeanTask as well. >> >> So If user registers two versions of TODO lean task definitions, first >> task will be TODO-1 and 2nd will be TODO-2. But only the latest will be >> active to create new lean tasks. >> >> Thanks, >> Hasitha. >> >> >> On Mon, Mar 30, 2015 at 5:16 PM, Yasima Dewmini <yas...@wso2.com> wrote: >> >>> Hi, >>> >>> This is regarding registering a lean task definition. >>> >>> According to the Human Task Specification, if an existing Lean Task >>> exists at the same name as the htd:tLeanTask/@Name, the WSHumanTask >>> Processor should return an htlt:illegalStateFault. >>> >>> But can't it be used with task versioning? >>> >>> Highly appreciate your comments. >>> >>> Thanks. >>> Yasima. >>> -- >>> K.Y.Dewmini >>> Software Engineer Intern >>> mobile: 0713117081 >>> >> >> >> >> -- >> Hasitha Aravinda, >> Software Engineer, >> WSO2 Inc. >> Email: hasi...@wso2.com >> Mobile: +94 71 8 210 200 >> >> > > > -- > Nandika Jayawardana > Senior Technical Lead > WSO2 Inc ; http://wso2.com > lean.enterprise.middleware > -- Hasitha Aravinda, Software Engineer, WSO2 Inc. Email: hasi...@wso2.com Mobile: +94 71 8 210 200
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture