Jan-Ole Esleben wrote:
The problem is that it isn't my design, and the design is part of a
contract. I can't really do anything about that (the major problem is
that there will be SOAP components that might even need to be
transparently integrated - which completely excludes ZEO).
That depends on your thinking...
I tried
doing my own commits, but it doesn't work, it just bombs earlier (no
matter where I do them).
You;re not giving us a lot of info here, but I think you need to read
the code in lib/python/ZPublisher in depth if you really need to play at
this level...
I really don't know why, my only guess is
that something about the transaction management breaks terribly when
you go back and forth between objects without them being able to track
it. Only I cannot figure out what.
Well, you could start by showing us the errors you're getting...
It is not possible to do _really_ explicit transaction management with
ZODB, is it?
Of course it is. But you're talking about Zope here, not ZODB. Zope
manages transactions so users don't often have to worry about them. If
you want to manage transactions within Zope, the nyou have to understadn
and co-operate with the transaction management that Zope does...
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
