Static Class Structure

• Client
  • Requires ServiceA and ServiceB objects.
  • Accepts the objects from the Injector.
  • Is independent of how the objects are created (which concrete classes are instantiated).
  • Doesn't know the Injector.
• Injector
  • Creates the ServiceA1 and ServiceB1 objects; creates the Client (if it doesn't already exist) and injects the objects into the Client.

Dynamic Object Collaboration

• In this sample scenario, an Injector object creates ServiceA1 and ServiceB1 objects. Thereafter, it creates a Client object and injects the ServiceA1 and ServiceB1 objects.
  Let's assume that the Injector uses a Configuration file that maps ServiceA and ServiceB interfaces to ServiceA1 and ServiceB1 implementations.
• The Injector starts with creating the ServiceA1 and ServiceB1 objects.
• Thereafter, the Injector creates the Client object and injects the ServiceA1 and ServiceB1 objects.
• The Client object can then use the ServiceA1 and ServiceB1 objects as required.
• See also Sample Code / Example1.