OpenERP 模块动态加载原理及启动代码分析

向右看齐 2022-08-08 06:19 135阅读 0赞

一般来说我们在编程中，对象定义都是预先定义好的。一些 OOP 语言（包括 Python/Java）允许对象是 自省的（也称为 反射）。即，自省对象能够描述自己：实例属于哪个类？类有哪些祖先？对象可以用哪些方法和属性？自省让处理对象的函数或方法根据传递给函数或方法的对象类型来做决定。即允许对象在运行时动态改变方法成员等属性。

得益于OpenERP ORM 模型的精巧设计，实际上 OpenERP 运行时也是动态读取模块信息并动态构建对象的。如在模块开发中，继承了 ‘res.users’, 新增一个方法或新增一个字段。在OpenERP 导入该模块后， OpenERP 会马上重构 ‘res.users’ 对象并将新增的方法或字段添加到该对象。那么，OpenERP 是如何做到这点的呢？ 让我们从OpenERP 的启动部分开始分析：

首先，OpenERP 启动相关的服务, 这时并没有建立数据库链接和载入对象

<table> 
 <tbody> 
 <tr> 
 <td> <pre>1
2
3
4
5
6
7
8
</pre> </td> 
 <td> <pre><code> if not config["stop_after_init"]: setup_pid_file() # Some module register themselves when they are loaded so we need the # services to be running before loading any registry. if config['workers']: openerp.service.start_services_workers() else: openerp.service.start_services() </code></pre> </td> 
 </tr> 
 </tbody> 
</table>

不过可以在配置文件中指定 ‘db\_name’ 参数，可以让 OpenERP 在启动时加载指定数据库的对象并启动 Cron。 实际生产环境中建议启用该参数，否则需要在启动OpenERP后，登录一次OpenERP 在会加载对象并启动CRON

<table> 
 <tbody> 
 <tr> 
 <td> <pre>1
2
3
</pre> </td> 
 <td> <pre><code> if config['db_name']: for dbname in config['db_name'].split(','): preload_registry(dbname) </code></pre> </td> 
 </tr> 
 </tbody> 
</table>

不指定 ‘db\_name’ 参数情况下，OpenERP 会直到用户登录时才会初始化指定数据库。

<table> 
 <tbody> 
 <tr> 
 <td> <pre>1
2
3
4
</pre> </td> 
 <td> <pre><code>def login(db, login, password): pool = pooler.get_pool(db) user_obj = pool.get('res.users') return user_obj.login(db, login, password) </code></pre> </td> 
 </tr> 
 </tbody> 
</table>

打开 get\_db 和 get\_db\_and\_pool 定义

顺藤摸瓜，看RegistryManager.new 定义

<table> 
 <tbody> 
 <tr> 
 <td> <pre>1
2
3
4
5
6
</pre> </td> 
 <td> <pre><code> try: # This should be a method on Registry openerp.modules.load_modules(registry.db, force_demo, status, update_module) except Exception: del cls.registries[db_name] raise </code></pre> </td> 
 </tr> 
 </tbody> 
</table>

然后看到 load\_modules, 终于要加载了，嘿嘿。

<table> 
 <tbody> 
 <tr> 
 <td> <pre>1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
</pre> </td> 
 <td> <pre><code> # STEP 1: LOAD BASE (must be done before module dependencies can be computed for later steps) graph = openerp.modules.graph.Graph() graph.add_module(cr, 'base', force) if not graph: _logger.critical('module base cannot be loaded! (hint: verify addons-path)') raise osv.osv.except_osv(_('Could not load base module'), _('module base cannot be loaded! (hint: verify addons-path)')) # processed_modules: for cleanup step after install # loaded_modules: to avoid double loading report = pool._assertion_report loaded_modules, processed_modules = load_module_graph(cr, graph, status, perform_checks=update_module, report=report) if tools.config['load_language']: for lang in tools.config['load_language'].split(','): tools.load_language(cr, lang) # STEP 2: Mark other modules to be loaded/updated if update_module: modobj = pool.get('ir.module.module') if ('base' in tools.config['init']) or ('base' in tools.config['update']): _logger.info('updating modules list') modobj.update_list(cr, SUPERUSER_ID) _check_module_names(cr, itertools.chain(tools.config['init'].keys(), tools.config['update'].keys())) mods = [k for k in tools.config['init'] if tools.config['init'][k]] if mods: ids = modobj.search(cr, SUPERUSER_ID, ['&amp;', ('state', '=', 'uninstalled'), ('name', 'in', mods)]) if ids: modobj.button_install(cr, SUPERUSER_ID, ids) mods = [k for k in tools.config['update'] if tools.config['update'][k]] if mods: ids = modobj.search(cr, SUPERUSER_ID, ['&amp;', ('state', '=', 'installed'), ('name', 'in', mods)]) if ids: modobj.button_upgrade(cr, SUPERUSER_ID, ids) cr.execute("update ir_module_module set state=%s where name=%s", ('installed', 'base')) # STEP 3: Load marked modules (skipping base which was done in STEP 1) # IMPORTANT: this is done in two parts, first loading all installed or # partially installed modules (i.e. installed/to upgrade), to # offer a consistent system to the second part: installing # newly selected modules. # We include the modules 'to remove' in the first step, because # they are part of the "currently installed" modules. They will # be dropped in STEP 6 later, before restarting the loading # process. states_to_load = ['installed', 'to upgrade', 'to remove'] processed = load_marked_modules(cr, graph, states_to_load, force, status, report, loaded_modules, update_module) processed_modules.extend(processed) if update_module: states_to_load = ['to install'] processed = load_marked_modules(cr, graph, states_to_load, force, status, report, loaded_modules, update_module) processed_modules.extend(processed) </code></pre> </td> 
 </tr> 
 </tbody> 
</table>

这里，第一步是加载核心模块 \[‘base’\]，第二步加载需要升级或预载的模块，第三步加载已安装的模块。实际加载语句是：

<table> 
 <tbody> 
 <tr> 
 <td> <pre>1
</pre> </td> 
 <td> <pre><code> processed = load_marked_modules(cr, graph, states_to_load, force, status, report, loaded_modules, update_module) </code></pre> </td> 
 </tr> 
 </tbody> 
</table>

查看 load\_marked\_module 定义：

重点是 load\_module\_graph

主要是下面2句，

<table> 
 <tbody> 
 <tr> 
 <td> <pre>1
2
3
</pre> </td> 
 <td> <pre><code> load_openerp_module(package.name) models = pool.load(cr, package) </code></pre> </td> 
 </tr> 
 </tbody> 
</table>

先看 load\_openerp\_module

上面代码中 import 了一个模块。如果您看过 digitalsatori 校长的大作 [ OpenERP与Python 元编程][OpenERP_Python], 下面就涉及到元类了：

import 的时候 就会调用元类的构造函数

上面的代码基本上就是将自身类加入到 module\_to\_models 字典中。

然后我们来看pool.load

这里我们可以看到 MetaModel 的身影，cls.create\_instance(self, cr) 这里就是动态构造对象的核心代码。

<table> 
 <tbody> 
 <tr> 
 <td> <pre>1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
</pre> </td> 
 <td> <pre><code> parent_names = getattr(cls, '_inherit', None) # 判断是否有继承父类 if parent_names: if isinstance(parent_names, (str, unicode)): name = cls._name or parent_names parent_names = [parent_names] else: name = cls._name if not name: raise TypeError('_name is mandatory in case of multiple inheritance') for parent_name in ((type(parent_names)==list) and parent_names or [parent_names]): # 读取父类 parent_model = pool.get(parent_name) if not parent_model: raise TypeError('The model "%s" specifies an unexisting parent class "%s"\n' 'You may need to add a dependency on the parent class\' module.' % (name, parent_name)) if not getattr(cls, '_original_module', None) and name == parent_model._name: cls._original_module = parent_model._original_module parent_class = parent_model.__class__ nattr = {} # 复制父类属性 for s in attributes: new = copy.copy(getattr(parent_model, s, {})) if s == '_columns': # Don't _inherit custom fields. for c in new.keys(): if new[c].manual: del new[c] # Duplicate float fields because they have a .digits # cache (which must be per-registry, not server-wide). for c in new.keys(): if new[c]._type == 'float': new[c] = copy.copy(new[c]) if hasattr(new, 'update'): new.update(cls.__dict__.get(s, {})) elif s=='_constraints': for c in cls.__dict__.get(s, []): exist = False for c2 in range(len(new)): #For _constraints, we should check field and methods as well if new[c2][2]==c[2] and (new[c2][0] == c[0] \ or getattr(new[c2][0],'__name__', True) == \ getattr(c[0],'__name__', False)): # If new class defines a constraint with # same function name, we let it override # the old one. new[c2] = c exist = True break if not exist: new.append(c) else: new.extend(cls.__dict__.get(s, [])) nattr[s] = new # Keep links to non-inherited constraints, e.g. useful when exporting translations nattr['_local_constraints'] = cls.__dict__.get('_constraints', []) nattr['_local_sql_constraints'] = cls.__dict__.get('_sql_constraints', []) # 调用元类构造函数 cls = type(name, (cls, parent_class), dict(nattr, _register=False)) else: cls._local_constraints = getattr(cls, '_constraints', []) cls._local_sql_constraints = getattr(cls, '_sql_constraints', []) if not getattr(cls, '_original_module', None): cls._original_module = cls._module # 构造对象 obj = object.__new__(cls) # 初始化对象 obj.__init__(pool, cr) return obj </code></pre> </td> 
 </tr> 
 </tbody> 
</table>

上面代码很重要，可以看到首先是判断该对象是否有继承父类，如果没有就直接构造，和动态没有什么关系。

如果有继承父类, 就复制父类属性, 这里就是动态构建类的做法。

假如有不同模块，都继承了同一个父类，那么如何保证类成员和属性是否加载完整或覆盖呢？ 答案在于这句代码：

<table> 
 <tbody> 
 <tr> 
 <td> <pre>1
</pre> </td> 
 <td> <pre><code> parent_model = pool.get(parent_name) </code></pre> </td> 
 </tr> 
 </tbody> 
</table>

Registry.get 的定义

<table> 
 <tbody> 
 <tr> 
 <td> <pre>1
2
3
</pre> </td> 
 <td> <pre><code> def get(self, model_name): """ Return a model for a given name or None if it doesn't exist.""" return self.models.get(model_name) </code></pre> </td> 
 </tr> 
 </tbody> 
</table>

最后看看obj.**init**(pool, cr)初始化对象，做了什么动作？

pool.add(self.\_name, self) 定义如下：

<table> 
 <tbody> 
 <tr> 
 <td> <pre>1
2
3
</pre> </td> 
 <td> <pre><code> def add(self, model_name, model): """ Add or replace a model in the registry.""" self.models[model_name] = model </code></pre> </td> 
 </tr> 
 </tbody> 
</table>

到这里应该很非常清楚，Registry.models 保存了对象的 model 信息。这样多个对象继承同一父类时，按照加载顺序先后动态构建相关的类。

至此，OpenERP 启动时动态加载模块分析完成。如模块安装、升级、卸载等, 则是通过 signal\_registry\_change 和 check\_registry\_signaling 处理，重新载入 Registry, 然后重新构建 OpenERP 对象。

来自：http://buke.github.io/blog/2013/02/26/openerp-dynamic-loading-and-booting-way/

[OpenERP_Python]: http://shine-it.net/index.php/topic,5771.msg14289.html