[Seaside] Omnibase transactions and Seaside transactions

[Cees de Groot]

To follow-up on my own ramblings, I think the best way would be to 
parallelize OmniBase and Seaside transactions - so I'm now storing 
OmniBase transactions in IATransaction, and 
IASession>>currentTransaction: also sets the current OmniBase transaction.

> edit: anItem
>   | ref |
>   ref := ReusableReference for: anItem
>   session isolate: [self callPage: (NewsItemEditor new item: ref)]
                       ^^^^^^^^^^^^^^^
   (yup, forgot to type that bit the previous message...)

With this example, that leaves one problem: when getting back from the 
edit, you want to refresh the list; therefore, after the 
#callPage:/isolate# are done, you need to invalidate the current 
transaction and setup a fresh one so that the next time the whole list 
of items is rendered, the updates from the database are shown.

Is it possible to switch transactions on-the-fly?