Community
Participate
Working Groups
The Transaction.OPTION_VALIDATE_EDIT option is not inherited by children of a CompositeEMFOperation. This causes the child operations to execute in their own new transactions, even when reuseParentTransaction is set to 'true', because the options of the child operation are always found to be different from those of the active transaction (which has the validate_edit option set). Bug 245446 was opened to request a general enhancement to allow options that don't affect the behaviour of a transaction (like validate_edit) to be excluded from the AbstractEMFOperation#optionsDiffer check, allowing clients to reuse the active write transaction in this case. This will likely require new API. In the mean time, I have opened this bug to track a fix that will address the specific effect of the Transaction.VALIDATE_EDIT option on transaction reuse. This fix will not require new API and should be suitable for the maintenance branch. I have set the severity to 'major' because we have found that these additional transactions have a significant negative impact on performance (see bug 141051).
Created attachment 112801 [details] Proposed patch and JUnit test
Cool, thanks! With a JUnit test! Let's see whether this can be squeaked into the Gany SR1, today. Looks like a pretty bad performance regression.
Committed the patch to the 1.2.2 branch. Thanks for the contribution!
Fix available in R1_2_maintenance: 1.2.2 (R200809171545).