model for reusable components that can be used in "cut-and-paste
i.e. can be configured and used in a visual development environment.
other component architectures, Java Beans doesn't rely on description
for the component's interface. Instead it relies on code introspection.
Since Java retains important information, such as method and variable
in the compiled code, it is possible to extract the interface of a
By using a few naming conventions for method names etc., it is possible
to dynamically inspect and configure an unknown bean 'on the fly', by
development environment, or even by an executing application.
Any Java class, or collection of classes, can constitute
a bean, there
is e.g. no "bean superclass" that needs to be subclassed. Additional
e.g. how the component should behave interact with the development
can be supplied in a special BeanInfo class - but this is not
A crucial factor for the cost effectiveness of any
is the time and labor needed for mastering it, and especially the art
creating new kinds of reusable components with it. Here, Java Beans
is a key strength. Learning how to create new Beans is a matter of
whereas it can take months to get even a modest grip of the art of
You will simply have your programmers productive very quickly with
Java Beans. The fact that Java is a nice language to program in, is of
course also a productivity booster.
Development Kit (BDK) is a little kit to get you started creating
configuring Beans. It has even a small graphical environment, a "Bean
where you can test and configure your beans, if you lack a graphical
environment. And if you need some help, you have the comp.lang.java.beans