Hi Subash, What requires you to delete the existing value? 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? 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
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
