Portal Type as Classes, ZODB Property Sheets: Ensure that they are reset on

other ZEO clients even if ZODB Components are not.

Steps to reproduce:

  1/ On zope1, view and edit a person to make sure class is fully loaded.
  2/ On zope2 add an interaction in person_interaction_workflow and add a script raising an exception.
  3/ Edit a person on zope2. The exception is raised, confirming that the interaction is called.

  When editing a person on zope1, the exception is not raised.

product/ERP5/ERP5Site.py

@@ -358,7 +358,10 @@ class ERP5Site(FolderMixIn, CMFSite, CacheCookieMixin):
         # This should only happen before erp5_core is installed
         synchronizeDynamicModules(self)
       else:
-        component_tool.reset()
+        if not component_tool.reset():
+          # Portal Types may have been reset even if Components haven't
+          # (change of Interaction Workflow...)
+          synchronizeDynamicModules(self)
 
     return self