Before bcoming a bean it is constructed and is just an object.
When the bean objects are given a bean context by the container then only then they attain beanness.
Beanness simply packages a lot of funtionality of various services into a ejb standerdised specification. Otherwise the same funtionality would have to be provided by the developer, or through reusable code library maintained by the developer or different vendors. The philosophy is if you have to overcome a same type of problem again and again lets standardise them. How exactly the solutions are standardised is the nitty and gritty of it and a matter of evolving into a better solutions over time.
P.S. Its my My view and I would like to hear more from others.
Weeds: because mother nature refuses to be your personal bitch. But this tiny ad is willing:
Devious Experiments for a Truly Passive Greenhouse!