> This isn't right: a z3c.form form is just a view like any other. It is
> looked up on the context and the request. In Dexterity (which I assume
> you're using?), that's going to be the content object.
Sorry, I think I mixed with zope.formlib. In any case I hope to find
the answer to the orignal question.
The original pattern which I copied is is here:
> I think you need to take a step back and look at how your form is set
> up, not dive into deep magic of persistence.
I don't think I am doing it incorrectly. The other reason of using
this pattern is that the behavior factory does not need to have a
write or (an extra) object load if the behavior is never set on the
context object. The default object returned by factory acts similar
than the persistent object and I can set the behavior defaults using
zope.schema - I don't need to do "if not set" logic anywhere else in
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org