Inversion of Control

IOC (Inversion Of Control) is a design pattern where developers delegate to an engine the control of their application in order to focus on business developments. The application life cycle (included in the control), which is not directly interesting when you develop a business application, is often delegated to a "support" implementation. This implementation is often develop once and proposed to all the business developers.

It is important to notice that true IOC modules are rare and are often configurable engine rather than complete frameworks. Among the existing, rare are those which differ from the Oracle/Sun approach. That's why the IOC framework Nuun IO and its kernel/plugin approach are completely unseen.

Content

Introduction
... Motivation
... Features
... Manifesto
User manual
... Kernel
...... Kernel Life Cycle
...... Kernel Configuration
... Plugin
...... Plugin Life cycle
...... Request API
...... Native Module
...... Dependencies
... Tests
...... Integration Tests
Advanced topics
... Design Best Practices
... Multi-Round Plugin
... Kernel param aliases
... SPI
...... DI Provider
...... Concern
...... Extension
Definitions
... Framework
... Entreprise Stack
... API
... SPI
... Library
... Inversion of Control
... Dependency Injection
Concepts
... UnitModule
... GlobalModule
... ObjectGraph

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Inversion of Control

Content

Clone this wiki locally