[transfer-dev] getParent still causes child object to be dirty?

I posted this about a year ago: http://groups.google.com/group/transfer-dev/browse_thread/thread/302a172cac3fe8d4/622750fc5b60f39c?lnk=gstq=getParent+dirty#622750fc5b60f39c We're now on Transfer 1.1, but getParentObject calls are still causing the child that initiated the call to be dirty. Did

[transfer-dev] Re: Many to Many, Leveraging columns in joining table

Thanks Mark, I started delving into some of these articles and am still stuck. I basically changed things around to look like this: package name=SiteArticles object name=category table=nis_categories decorator=transfer.decorators.categoryDecorator

[transfer-dev] Re: getParent still causes child object to be dirty?

Hey, looks like the getParent() isDirty issue got missed in the jumble. Looking at the code now, seems like an easy fix. Running unit tests now. Mark On Fri, Apr 10, 2009 at 1:26 AM, Jon Schultz jon.c.schu...@gmail.com wrote: I posted this about a year ago: