I really thought there is no one who can teach complicated subjects with ease. But finally I found one. I really respect you to the core of my heart. I wish that I get a chance to see you one day. Thank you brother. Thanks a lot. You are helping us in a manner which is non comparable. I wish I can help others the way you are helping. Really touched. I was really hungry to learn all these things. But no one as good as you. Thanks a lot. I can not explain further.
Your tutorials are really helpful. I was exposed to Spring briefly before, and it left me confused and irritated. Your tutorials are simple yet very useful and leave you with a great feeling of deep understanding of what is going on and accomplishment. I really feel comfortable with Spring and Maven after I've watched your tutorials. Thank you so much! You're doing an amazing job.
Awesome as usual. One question though. in Spring.xml, when you changed the that points to class Triangle, does this mean for the Circle bean, do we have to have another that points to Circle class ? I thought bean IDs should be unique? Kindly explain. Thanks again !
@Baloux maybe what he meant was that there can be a new shape suppose rectangle. So for this new shape we need to just add the conf in the bean xml and then we can store it in the shape type ref. During this step we need to make sure that rectangle implements Shape
awesome tutorial only suggestion is that are you using old TVS gold keyboard or what making a lot noise while typing....lol...just kidding ... your tutorial is awesome ...
I feel really stupid, but what is the difference between "Circle circle = (Circle) context.getBean("circle");" and "Shape shape = (Shape) context.getBean("circle");" The only advantage I see is that I would only have to change the circle after getBean once if I want it to be a triangle instead of changing "circle" 4 times to triangle. But I can see no functional difference.
@Eduardo Carrillo Thank you, we need to move this question and this comment to the top! I had the same question, and searched for a while before I came across your response. One more option could be, to use alias shape as your controlling point, and switch around what it refers to (circle/triangle)
These tutorials are very good, but I would like to point out one thing that is not mentioned. Before seeing this particular video, I got the impression that all the objects/classes that will be used in the transactions to the database will also follow this dependency injection stuff, but that is not right. I found that information from some other source. It should be mentioned in this tutorials in the beginning about this clear difference that we do the dependency injection stuff for the classes like the dao, service etc and not the beans that are saved in the database. Despite all this, the tutorials are so helpful.
+Den Uil - you should write interfeces when you want to give a names of the methods but not the implementations / you will pass implementation to class witch implements interface.
A weird behavior - if someone can explain, much appreciated: spring.xml ------------------------
DrawingApp Class -------------------------------------- Shape shape = (Shape) context.getBean("circle"); shape.draw(); Output: --------------------- Why is myInit() and myDestroy() class called, when invoking "circle" --------------------- init-method myInit called PointA: 0,0 Jan 15, 2018 1:13:59 PM org.springframework.context.support.ClassPathXmlApplicationContext doClose INFO: Closing org.springframework.context.support.ClassPathXmlApplicationContext@3d71d552: startup date [Mon Jan 15 13:13:58 CST 2018]; root of context hierarchy destroy-method myDestroy called
Since all the beans are a singleton, so all the beans are initialized when application-context is initialized. Therefore, along with all the objects, triangle object is also created, hence init-method, and destroy-methods are called. Hope it helps. :)
I really thought there is no one who can teach complicated subjects with ease. But finally I found one. I really respect you to the core of my heart. I wish that I get a chance to see you one day. Thank you brother. Thanks a lot. You are helping us in a manner which is non comparable. I wish I can help others the way you are helping. Really touched. I was really hungry to learn all these things. But no one as good as you. Thanks a lot. I can not explain further.
es un buen pibe que explica muy bien, deberia ser un profesor de universidad
I've been waiting so long for someone to properly explain the purpose of Interfaces. Thank you koushk.
Your tutorials are really helpful. I was exposed to Spring briefly before, and it left me confused and irritated. Your tutorials are simple yet very useful and leave you with a great feeling of deep understanding of what is going on and accomplishment. I really feel comfortable with Spring and Maven after I've watched your tutorials. Thank you so much! You're doing an amazing job.
Hi Kaushik, You are doing a wonderful job, your tutorials are clean and sharp. Thanks for your time and sharing knowledge.
Thanks such a good tutorial. Now Finally I know why we need abstract clases n interfaces and why these are imp..
Words will be few to thank you.. Please keep up the good work..
Your tutorials are very useful. Great job.
This concept works the same way for abstract classes also. In fact, shape is more suited as an abstract class rather than an interface.
Hi Kaushik, Your Tutorials are really helpful!! Thanks a lot!! Please Share some tutorials on Spring MVC Framework.
Thanks a lot!!
Yeah, that's would be really awesome. Looking forward to that. And thanks for your great tutorials Kaushik
Excellent work! you make it look so easy! congratulation on all your hard work
so its like polymorphism? ex: Animal animal = new Dog(); except it uses dependency injection instead of creating the object using 'new' keyword?
Awesome as usual. One question though. in Spring.xml, when you changed the that points to class Triangle, does this mean for the Circle bean, do we have to have another that points to Circle class ? I thought bean IDs should be unique? Kindly explain. Thanks again !
Yeah he's awesome.
_Doesn't reply to his customers even after 5 years..._
@Baloux maybe what he meant was that there can be a new shape suppose rectangle. So for this new shape we need to just add the conf in the bean xml and then we can store it in the shape type ref. During this step we need to make sure that rectangle implements Shape
awesome tutorial only suggestion is that are you using old TVS gold keyboard or what making a lot noise while typing....lol...just kidding ... your tutorial is awesome ...
the same as LeBadman, none can't explain properly the use of the interfaces on spring THANK YOU!!!
So, by default we should always make an interface of an class, so that if there is a new version it can be more easily replaced?
Den Uil yup
I feel really stupid, but what is the difference between "Circle circle = (Circle) context.getBean("circle");" and "Shape shape = (Shape) context.getBean("circle");" The only advantage I see is that I would only have to change the circle after getBean once if I want it to be a triangle instead of changing "circle" 4 times to triangle. But I can see no functional difference.
@Eduardo Carrillo Thank you, we need to move this question and this comment to the top!
I had the same question, and searched for a while before I came across your response.
One more option could be, to use alias shape as your controlling point, and switch around what it refers to (circle/triangle)
Thank you for asking this question, and making the space for someone to respond. Saved me a lot of searching...
awesome koushk....keep going
These tutorials are very good, but I would like to point out one thing that is not mentioned. Before seeing this particular video, I got the impression that all the objects/classes that will be used in the transactions to the database will also follow this dependency injection stuff, but that is not right. I found that information from some other source. It should be mentioned in this tutorials in the beginning about this clear difference that we do the dependency injection stuff for the classes like the dao, service etc and not the beans that are saved in the database. Despite all this, the tutorials are so helpful.
Great tutorials koushik...
any chance for web mvc tutorials??
Awesome👍
+Den Uil - you should write interfeces when you want to give a names of the methods but not the implementations / you will pass implementation to class witch implements interface.
+EasyTutorials or you want to do polymorphysm
Instead of typing System.out.println all the time, you can type syso and ctrl+space . This would save lot of time :)
you are the best ;)
Where can I download the code from? Do you have a link?
Yes, yes and furthermore yes!
Why do you punch your enter and delete keys?
hahahahah lol
Awesome
did spring mvc tutorial came ?
no
great.
Strategy Pattern
Sir the video is not working !!! Its giving error..
use alias instead of changing bean id
Please try to avoid the keyboard typing sound in the video, its very irritating
Anyone watching in 2020.
A weird behavior - if someone can explain, much appreciated:
spring.xml
------------------------
DrawingApp Class
--------------------------------------
Shape shape = (Shape) context.getBean("circle");
shape.draw();
Output:
---------------------
Why is myInit() and myDestroy() class called, when invoking "circle"
---------------------
init-method myInit called
PointA: 0,0
Jan 15, 2018 1:13:59 PM org.springframework.context.support.ClassPathXmlApplicationContext doClose
INFO: Closing org.springframework.context.support.ClassPathXmlApplicationContext@3d71d552: startup date [Mon Jan 15 13:13:58 CST 2018]; root of context hierarchy
destroy-method myDestroy called
Since all the beans are a singleton, so all the beans are initialized when application-context is initialized.
Therefore, along with all the objects, triangle object is also created, hence init-method, and destroy-methods are called. Hope it helps. :)
Bro You are a good trainer but bad coder.. If I were you I would have used copy paste from everywhere. but you write everything
IDK, i like his style. Just saying...
recorded in 2011