This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.Find sources: "JavaBeans" – news · newspapers · books · scholar · JSTOR (June 2016) (Learn how and when to remove this template message) This article is written like a manual or guide. Please help rewrite this article and remove advice or instruction. (October 2012) (Learn how and when to remove this template message)

In computing based on the Java Platform, JavaBeans is a technology developed by Sun Microsystems and released in 1996, as part of JDK 1.1.

The 'beans' of JavaBeans are classes that encapsulate one or more objects into a single standardized object (the bean). This standardization allows the beans to be handled in a more generic fashion, allowing easier code reuse and introspection. This in turn allows the beans to be treated as software components, and to be manipulated visually by editors and IDEs without needing any initial configuration, or to know any internal implementation details.

As part of the standardization, all beans must be serializable, have a zero-argument constructor, and allow access to properties using getter and setter methods.


Introspection is a process of analyzing a Bean to determine its capabilities. This is an essential feature of the Java Beans specification because it allows another application, such as a design tool, to obtain information about a component.
A property is a subset of a Bean's state. The values assigned to the properties determine the behaviour and appearance of that component. They are set through a setter method and can be obtained by a getter method.
A customizer can provide a step-by-step guide that the process must follow to use the component in a specific context.
Beans may interact with the EventObject EventListener model.[clarification needed]
Persistence is the ability to save the current state of a Bean, including the values of a Bean's properties and instance variables, to nonvolatile storage and to retrieve them at a later time.
A Bean should use accessor methods to encapsulate the properties. A Bean can provide other methods for business logic not related to the access to the properties.



JavaBeans API

The JavaBeans functionality is provided by a set of classes and interfaces in the java.beans package.

Interface Description
AppletInitializer Methods in this interface are used to initialize Beans that are also applets.
BeanInfo This interface allows the designer to specify information about the events, methods and properties of a Bean.
Customizer This interface allows the designer to provide a graphical user interface through which a bean may be configured.
DesignMode Methods in this interface determine if a bean is executing in design mode.
ExceptionListener A method in this interface is invoked when an exception has occurred.
PropertyChangeListener A method in this interface is invoked when a bound property is changed.
PropertyEditor Objects that implement this interface allow the designer to change and display property values.
VetoableChangeListener A method in this interface is invoked when a Constrained property is changed.
Visibility Methods in this interface allow a bean to execute in environments where the GUI is not available.

JavaBean conventions

In order to function as a JavaBean class, an object class must obey certain conventions about method naming, construction, and behaviour. These conventions make it possible to have tools that can use, reuse, replace, and connect Java Beans.

The required conventions are as follows:

Code example

package player;

public class PersonBean implements {

    /** Properties **/
    private boolean deceased = false;

    private List list;

    /** Property "name", readable/writable. */
    private String name = null;

    /** No-arg constructor (takes no arguments). */
    public PersonBean() {

    public List getList() {
        return list;
    public void setList(final List list) {
        this.list = list;

     * Getter for property "name".
    public String getName() {
        return name;

     * Setter for property "name".
     * @param value
    public void setName(final String value) { = value;

     * Getter for property "deceased"
     * Different syntax for a boolean field (is vs get)
    public boolean isDeceased() {
        return deceased;

     * Setter for property "deceased".
     * @param value
    public void setDeceased(boolean value) {
        deceased = value;

import player.PersonBean;

 * Class "TestPersonBean".
public class TestPersonBean {
     * Tester method "main" for class "PersonBean".
     * @param arguments
    public static void main(final String[] arguments) {
        final PersonBean person = new PersonBean();

        person.setList(new ArrayList());

        // Output: "Bob [alive]"
        System.out.println(person.isDeceased() ? " [deceased]" : " [alive]");
<jsp:useBean id="person" class="player.PersonBean" scope="page"/>
<jsp:setProperty name="person" property="*"/>

        Name: <jsp:getProperty name="person" property="name"/><br/>
        Deceased? <jsp:getProperty name="person" property="deceased"/><br/>
        <form name="beanTest" method="POST" action="testPersonBean.jsp">
            Enter a name: <input type="text" name="name" size="50"><br/>
            Choose an option:
            <select name="deceased">
                <option value="false">Alive</option>
                <option value="true">Dead</option>
            <input type="submit" value="Test the Bean">

See also


  1. ^ a b Bloch, Joshua (2008). Effective Java (Second ed.). Addison-Wesley. p. 13. ISBN 978-0-321-35668-0.