Hi Subash, If that's the case, we can track this right? Old one had it, new one does not == deletion?
Thanks, Senaka. On Wed, Dec 5, 2012 at 11:21 AM, Subash Chaturanga <[email protected]> wrote: > > > On Wed, Dec 5, 2012 at 11:16 AM, Senaka Fernando <[email protected]> wrote: > >> Hi Subash, >> >> Its a 1-1 replace. So, if you delete something and save, that should go. >> If the old entry stays, that means we are appending not replacing. >> > > No that's not how it happens. It gets the old artifact. And set the all > updated attributes from the new artifact to the old one. Then consider the > old one as the new one. > >> >> Thanks, >> Senaka. >> >> >> On Wed, Dec 5, 2012 at 11:11 AM, Subash Chaturanga <[email protected]>wrote: >> >>> >>> >>> On Wed, Dec 5, 2012 at 10:40 AM, Senaka Fernando <[email protected]>wrote: >>> >>>> Hi Subash, >>>> >>>> ARGH, I misunderstood. I was thinking you were talking about an Asset >>>> itself, but not a field in an Asset. What you are saying did work in the >>>> past, and it is definitely a regression of some sort. >>>> >>> >>> I don't think this is a regression. With the current model, we can't >>> achieve aforementioned scenario, since we pass only the content which has >>> updated (updated as an empty field cannot be tracked back). >>> >>> >>>> >>>> Thanks, >>>> Senaka. >>>> >>>> >>>> On Wed, Dec 5, 2012 at 10:35 AM, Subash Chaturanga <[email protected]>wrote: >>>> >>>>> >>>>> >>>>> On Wed, Dec 5, 2012 at 9:57 AM, Senaka Fernando <[email protected]>wrote: >>>>> >>>>>> Hi Subash, >>>>>> >>>>>> What requires you to delete the existing value? >>>>>> >>>>> >>>>> i.e A user should be able to delete a field value isn't it. Say for an >>>>> example I want to delete the description/comment field in an RXT. >>>>> >>>>> >>>>>> Our assumption is such would only be done in an LC Executor and those >>>>>> do handle that situation. In other cases, this would only happen if you >>>>>> change any attribute that changes the path in which the asset is stored. >>>>>> We >>>>>> decided not to over complicate that situation. This is why we don't have >>>>>> this. >>>>>> >>>>>> But, also, when it comes to an asset, if it was the exact same asset >>>>>> that is being saved, the UUID won't change. You can use it internally to >>>>>> compute the previous path. Is this condition violated or did someone >>>>>> simply >>>>>> write some logic that works for Services but not RXT based assets in the >>>>>> past? >>>>>> >>>>> I have not tested this particular scenario in past, but now this >>>>> fails for all RXTs. >>>>> >>>>> >>>>>> Thanks, >>>>>> Senaka. >>>>>> >>>>>> On Wed, Dec 5, 2012 at 1:36 AM, Subash Chaturanga <[email protected]>wrote: >>>>>> >>>>>>> Hi, >>>>>>> $subject ? Because of this, if some body deletes an existing value >>>>>>> and save the content, it will not get tracked as an edited one. >>>>>>> And when updating, it writes all the elements in the new artifact to >>>>>>> the old one and save the old one as the updated one. >>>>>>> >>>>>>> With this model, no one can't delete an existing value of an >>>>>>> artifact and save it. >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Subash Chaturanga >>>>>>> Software Engineer >>>>>>> WSO2 Inc. http://wso2.com >>>>>>> >>>>>>> email - [email protected] >>>>>>> phone - 077 2225922 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> * <http://wso2con.com/> >>>>>> * >>>>>> * >>>>>> >>>>>> Senaka Fernando* >>>>>> Member - Integration Technologies Management Committee; >>>>>> Technical Lead; WSO2 Inc.; http://wso2.com* >>>>>> Member; Apache Software Foundation; http://apache.org >>>>>> >>>>>> E-mail: senaka AT wso2.com >>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>>>> Linked-In: http://linkedin.com/in/senakafernando >>>>>> >>>>>> *Lean . Enterprise . Middleware >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Subash Chaturanga >>>>> Software Engineer >>>>> WSO2 Inc. http://wso2.com >>>>> >>>>> email - [email protected] >>>>> phone - 077 2225922 >>>>> >>>>> >>>> >>>> >>>> -- >>>> * <http://wso2con.com/> >>>> * >>>> * >>>> >>>> Senaka Fernando* >>>> Member - Integration Technologies Management Committee; >>>> Technical Lead; WSO2 Inc.; http://wso2.com* >>>> Member; Apache Software Foundation; http://apache.org >>>> >>>> E-mail: senaka AT wso2.com >>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>> Linked-In: http://linkedin.com/in/senakafernando >>>> >>>> *Lean . Enterprise . Middleware >>>> >>>> >>> >>> >>> -- >>> >>> Subash Chaturanga >>> Software Engineer >>> WSO2 Inc. http://wso2.com >>> >>> email - [email protected] >>> phone - 077 2225922 >>> >>> >> >> >> -- >> * <http://wso2con.com/> >> * >> * >> >> Senaka Fernando* >> Member - Integration Technologies Management Committee; >> Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> > > > -- > > Subash Chaturanga > Software Engineer > WSO2 Inc. http://wso2.com > > email - [email protected] > phone - 077 2225922 > > -- * <http://wso2con.com/> * * Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
