Since I'm not know in deep the mmbase transaction manager, I don't think this is a good fix and probabily it introduces new bugs, however it may be helpful for a real solution implementation. I would like to hear your comments.
Maybe I'm thinking too simple, but isn't it a lot easier to just drop the throwing of the exception (lines 81-83 in trasnbacvtio Manager) than
adding lots of code that is not optimal?
After all, the problem is that (for a reason that is beyond my grasp) I cannot 'add' a node to a transaction if it is already in it. I say we fix that rather than add code.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
