Component registration flow
When a component is registered on the MicroKernel, a chain of actions happens:
- A new ComponentModel is created for the component
- All registered contributors have a change to change or add something to the ComponentModel
- A new Handler is requested from the HandlerFactory
- The new handler checks the ComponentModel information and:
- Creates the ComponentActivator
- Creates the LifestyleManager
- Starts the check for the minimal set of dependencies
If the minimal set of dependencies are not reachable, the handler sets its state to WaitingDependency and returns.
Found an error? Something inaccurate? Help us improve the documentation
Generated by Castle Anakia.
Sponsored by 
Castle Stronghold.