[Zope-CMF] Re: Replication And Workflows - "Nightmare of CMF Street"

[Seb Bacon]

Tres Seaver wrote:
> On Tue, 2003-09-16 at 15:23, Norfleet, Sheppard S. wrote:
>>Replication And Workflows
>>"Nightmare of CMF Street"
>>
>>I am having a heck of a time with my application level replication.  I am
>>able to recreate the object, but apparently the workflow_history attribute
>>does not seem to travel with the object its tied to.  This seems to be the
>>case because after I assign the object to the parent on the mirror machine
>>using xxx._setObject() of the replicated object, the state always seems to
>>fall back to 'created'.  

> In earlier verisons of CMF, the workflow was notified that cloned
> objects had been created via the object's 'manage_afterAdd' method; 
> more recent versions correct this to do the notification in
> 'manage_afterClone'.  The symptom in those case was that objects would
> "revert" to the private workflow state when copied and pasted between
> folders.

I'm confused.  If the notification is in manage_afterClone, why won't 
this *continue* to give the "reset" symptom when objects are 
copy-and-pasted?

I think perhaps I misunderstand the intent of manage_afterClone..?  I 
only realised it existed recently after 4 years of using Zope!

seb