SolverTool, as a Type Provider, needs to be handled carefully:

in fact, accessing erp5.portal_types will try loading the contents
of portal_solvers as well...


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

product/ERP5Type/dynamic/portal_type_class.py

@@ -118,10 +118,12 @@ property_sheet_generating_portal_type_set = set()
 # Property Sheet to allow the outer (which will actually be stored in
 # 'erp5.portal_type') to be fully generated.
 core_portal_type_class_dict = {
-  'Base Type': {'type_class': 'ERP5TypeInformation',
-                'generating': False},
-  'Types Tool': {'type_class': 'TypesTool',
-                 'generating': False}
+  'Base Type':    {'type_class': 'ERP5TypeInformation',
+                   'generating': False},
+  'Types Tool':   {'type_class': 'TypesTool',
+                   'generating': False},
+  'Solver Tool': {'type_class': 'SolverTool',
+                  'generating': False}
   }
 
 def generatePortalTypeClass(portal_type_name):