Why to use beans?

Question

why to use beans?

Answer 1

One) I think you need to read up on the bean specification and examine the API before you can expect someone to help you understand it.
Two) Java beans are still java classes. There are special interfaces and classes which can be used to better aid visual tools or any other tool actually that may use beans, but they are not required to be created for any given bean. I think the notion that "beans" add over head is simply invalid as a bean can be as simple as a class that has a property name and has methods public void setName(String) and public String getName(). The only thing that makes this a bean is naming conventions. There are helper classes that pick out these patterns for IDE's to make it easier for them or any other bean friendly environment to access classes designed a special way (those that adhere to the bean standards/patterns). So, other than some special property customizer gui's and other helper classes that are not required to be used, if you know how to use setter and getter methods you know how to create at least simple beans, and bean friendly environments can more easily use your class because they can detect the bean patterns and at least know how to make your class/bean available and useable in their context. That's the biggest advantage...a standardized approach to a certain portion of the design that allows applications to access generic components in a usual/logical/standard fashion.
Wade