2010-07-24 yo

* Fix the bug that generates multiple Root Applied Rules partially. Ultimately, we should always use the same script (i.e. Delivery_updateSimulation), otherwise it is too hard to make sure that all callers are serialized.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@37261 20353a03-c40f-0410-a6d1-a30d3c3de9de

bt5/erp5_base/SkinTemplateItem/portal_skins/erp5_base/Delivery_updateSimulation.xml

@@ -61,15 +61,24 @@ tag = delivery_path + \'_updateAppliedRule\'\n
 \n
 priority = 3\n
 \n
+# These parameters are passed to activate for expand and reindexObject,\n
+# so Delivery_updateAppliedRule will wait for the creation and indexing of\n
+# Applied Rules and Simulation Movements by another Delivery_updateAppliedRule.\n
+# This is required for finding an existing Applied Rule by the catalog, and\n
+# avoiding needless conflicts.\n
 activate_kw = { \n
   \'tag\': expand_tag,\n
   \'priority\': priority,\n
 }\n
+\n
+# Serialization is required for avoiding parallel executions of updateAppliedRule\n
+# which may generate multiple Root Applied Rules.\n
 delivery.activate(\n
     after_path_and_method_id=path_and_method_id,\n
     after_tag=expand_tag,\n
     tag=tag,\n
     priority=priority,\n
+    serialization_tag=delivery_path,\n
     ).Delivery_updateAppliedRule(activate_kw=activate_kw)\n
 </string> </value>
         </item>

bt5/erp5_base/bt/change_log

+2010-07-24 yo
+* Fix the bug that generates multiple Root Applied Rules partially. Ultimately, we should always use the same script (i.e. Delivery_updateSimulation), otherwise it is too hard to make sure that all callers are serialized.
+
 2010-07-14 yusei
 * Set reference field to Rounding Model view form.
 

bt5/erp5_base/bt/revision

-815
+816
\ No newline at end of file