Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
Instructor: In this video,
we're gonna learn about constructor injection
and how it works behind the scenes.
Now, how does Spring process your application?
We have our interface for coach,
we have our cricket coach implementation,
and then we have our demo controller.
And so the Spring framework will perform operations for you
behind the scenes for processing these items.
Behind the scenes, Spring will create a new instance
of your coach, new cricket coach.
It'll also perform constructor injection
with your demo controller.
It'll actually inject the coach into the demo controller.
And remember, the whole idea of injection is
that there's a dependency or a helper.
So in this case, the coach is a dependency or a helper
for the actual controller.
The new keyword, is that it?
So you're probably wondering, is it just the new keyword?
I really don't need Spring for this. I could do this myself.
Okay, and you're saying, what's the point of Spring
if it's just the new keyword?
Come on. It has to be more to it than that.
Well, it actually is.
So Spring is more than just inversion of control
and it's more than just dependency injection.
For small basic applications like we're building here,
it may be hard to see the real benefits of Spring.
But now, Spring is designed for enterprise applications.
All right, so it's targeted for enterprise,
real-time, real-world applications.
And Spring provides features such as database access
and transactions, REST APIs, Web MVC, security, and so on.
Later in the course,
we'll build a real CRUD REST API with database access
and so you'll see these Spring features in action.
So a lot of good things are coming.
So again, Spring is more than just ILC MDI.
There's a lot of other really good features
that you can make use of with Spring.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.