The document discusses the Spring Framework and inversion of control (IoC). It explains that IoC is an OOP principle where modules depend on abstractions rather than concrete classes. This reduces coupling between modules. The Spring Framework implements IoC through dependency injection and a service locator. Dependency injection allows a client to set the dependencies of a module. The Spring Framework is lightweight, open source, and easy to test. It uses either XML or annotation-based configuration for dependency injection or service location.

1. Spring
Framework &
Inversion of
Control
By Nazim Sitmanbetov

2. Preconditions
 Keep
calm
 Sit back
 Relax

3. Inversion of Control
 OOP
principle, not design pattern
 One of

4. Principle in OOP
 Modules
depend on abstractions
 Low level modules do not depend on
high level modules

5. Modules depend on
abstractions
Bad
Good

6. Low level modules do not
depend on high level modules
Bad
Tip: Avoid cyclic dependencies
Good

7. IoC implementations
 Factory
Method
 Service Locator
 Dependency Injection (DI)

8. Factory Method

9. Service Locator

10. Dependency Injection
 Allow
client of module to set dependency
Module
Client

11. Achievement unlocked

12. Framework
 Java
 Light-weight
 Open
Source

13. What means Light-Weight?
 No
container requirements
 Quick start
 Application easy-to-test

14. Spring & IoC
 Dependency
Injection
 Service Locator

15. Spring & Dependency
Injection
XML Based Configuration
mcdonalds-with-kazatin.xml
Java Program

16. Spring & Service Locator
Annotation Based
mcdonalds-locator.xml

17. Spring & Service Locator

18. Dependency Injection vs
Service Locator
DI
Service Locator
• Imperative
• Can be used with
existing classes
• Declarative
• Need to modify
existing classes

19. Spring components

20. Time to cook