CoreandServices.book - Ocean - Schlumberger

The Ocean Module
between different modules and allows modules to use services and features of other
modules. The order of execution between modules is undefined, with the exception that
the ModuleDependency attribute enforces ordering when required.
Initialize
Integrate
IntegratePresentation
Disintegrate
Dispose
Initialize
Integrate
IntegratePresentation
Disintegrate
Dispose
Initialize
Integrate
IntegratePresentation
Disintegrate
Dispose
all finished
before next
stage
Fig. 3-3 Module Lifecycle Phase Execution
Default Constructor
During the product startup the Ocean Core will load modules as defined in the
configuration file for the product family. Modules may also be loaded dynamically as
discussed in “Dynamic Module Loading” on page 3-34. The Ocean Core will call the default
constructor to instantiate each module. All modules must have a default constructor as
defined by the interface. The constructor should:
• Acquire the module’s license
• Initialize any private fields for the module
• Acquire any resources the module needs.
The module license is acquired from the license provider defined for the module class by
the LicenseProvider attribute. The license provider may be whatever licensing
mechanism you choose as long as it properly derives from the
System.ComponentModel.LicenseProvider class.
The code sample below shows the FooBar licensing provider defined for the
LicenseProvider attribute. The actual license is acquired by the
LicenseManager.Validate method, which is given the type of our module class. If a
Schlumberger Private
Ocean Core 3-25