Hi Joe,

Am 08.06.2011, 11:05 Uhr, schrieb Joe Steeve <j...@hipro.co.in>:

> Supposing, we have a form action like:
>        @form.action('Apply')
>         def handle_edit(self, action, data):
>               self.context.name += "Blah"

> This change is visible in subsequent requests. i.e if we view this
> object via another form, we can see the modification. However, if we
> restart the server (bluebream), this change is lost. The same thing
> happens when we use "form.applyData". If we 'notify'
> ObjectModifiedEvent, this does not happen.

> Since the object's modification is visible across requests, I am
> assuming that the transaction mechanism 'did' apply the changes to the
> object.

> But, it did not get to the disk :-/

I'm surprised at this but I'm not familiar with Bluebream's transactional  
processing. The quickest thing to do is to reenable notification and add a  
debug so that you can follow all the subscription calls and see what you  
need to call.

Why do want to disable notification?

Charlie Clark
Managing Director
Clark Consulting & Research
German Office
Helmholtzstr. 20
D- 40215
Tel: +49-211-600-3657
Mobile: +49-178-782-6226
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to