Why do we need beans and/or spring in Java?

Before we go into programming, let's talk about real life. Let's say you are at home, and your kids are bored. You decide to buy a new toy for them. So, you go to the toy store, and ask them to give you a plane. read more

Secondly we DON’T need spring, in fact it is outdated and if you have a choice I would advice a more modern framework that is cleaner and leaner. Spring is a beast, overbearing and a bit overused. There are lots of alternatives to Spring that have lots of advantages. read more

POJO is an orthogonal concept and a Java bean may easily also be a POJO. You seem to be contemplating beans in the context of the Spring IoC container. Spring uses the term"bean" in quite a loose sense and the actual objects may not even comply with the JavaBeans specification. read more

Java Bean is a java class it should have a no-arg constructor, it should be Serializable, it should provide methods to set and get the values of the properties, known as getter and setter methods.They are used to encapsulate many objects into a single object (the bean), so that they can be passed around as a single bean object instead of as multiple individual objects. read more

Before we go into programming, let’s talk about real life. Let’s say you are at home, and your kids are bored. You decide to buy a new toy for them. So, you go to the toy store, and ask them to give you a plane. read more

POJO is an orthogonal concept and a Java bean may easily also be a POJO. You seem to be contemplating beans in the context of the Spring IoC container. Spring uses the term"bean" in quite a loose sense and the actual objects may not even comply with the JavaBeans specification. Most typically they provide only a setter (no getter). read more