Notes about Spring IoC

A p p B l i e i i n a n c t n t a e F e t r a r i f c f o a t a n c o c C e r e o y n t e x t - a - - - - d p m d e m e a ` r a s a e v p W o n s s e p e v a f i s n l b i g e e a t i A d i a r g c p e n t e p a p s g u i u t l r n r b i i c a e t e l o c o n s e s i n a n y : r o c - t f g u a l i i t r r t a o g y a c i y n u p t e o e C r e i n r o a o h n t o n a s t i f n p e o w d e x n o i l c t b t i i ` m j h n f e e g i f c c S c o h t p ( r a r i c n i n o u i n t n s s g e t e m ' r e s n x i c a t n a A t s p O i w a P o s e b n u b l f a c e e l h a a i p t t z a p o u a s l r t i e i t c s o h a n e t ) i o n s

In Spring, the objects that form the backbone of your application and that are managed by the Spring IoC container are called beans. A bean is an object that is instantiated, assembled, and managed by a Spring IoC container. Otherwise, a bean is simply one of many objects in your application. Beans, and the dependecies among them, are reflected in the configuration metadata used by a container.