Ok Fabio. The DefaultSaveOrUpdateCopyEventListener inherits from the DefaultMergeEventListener and there is no overriding behaviour in this derived class. So the implementations are close to 99% the same already. The Merge cascade changes I've made are therefore already the same for SaveOrUpdateCopy.
You say the SaveOrUpdateCopy function is 'disabled'. How so? I haven't seen any evidence of this.. Regards Julian On 22 Jan 2011 21:33, "Fabio Maulo" <[email protected]> wrote: > Hi. > It is ok to mark SaveOrUpdateCopy as obsolete but we can't apply all changes > as we had already disabled the function. > > In practice if we want to say that SaveOrUpdateCopy is "identical" to Merge > and we have already applied some changes to the cascade actions we have to > change even the method SessionImpl.SaveOrUpdateCopy and instead fire the > event FireSaveOrUpdateCopy we have to fire FireMerge. > > care with porting... we know that we don't have all tests really needed. > > -- > Fabio Maulo
