The best way to build a bean is to start with a simple example. Start with the most basic possible bean, then add a property to it. First the basic bean:

Basic Bean (Acme01Bean)

import java.awt.*;
import java.io.Serializable;


public class Acme01Bean extends Canvas implements Serializable {

    public Acme01Bean() {
        resize(60,40);
    }

    public void paint(Graphics g) {
        g.setColor(Color.blue);
        g.fillRect(20, 5, 20, 30);
    }
}

First of all, a bean must implement the Serializable interface. Objects that support this interface can save and restore their state from disk. Beans that have been customized (usually by editing their properties in builder tools) must be able to save and restore themselves on request. Normally, there is little you need to do other than declare Serializable in the class definition. Because most AWT objects in JDK 1.1 already know how to serialize themselves, there's generally nothing to do beyond the declaration. A possible exception is if your objects have an instance variable that needs to override its default behavior for serialization. For example a thread's execution state needs special handling. An example is given in a later lesson.

When you drop this bean into the BeanBox, you'll see it appear on the palette of ToolBox components.

When the paint method is invoked by the builder tool (BeanBox in this case), all you see is a simple blue colored rectangle. The boxed area outside of the blue rectangle, merely indicates that this is the currently selected bean; it is not part of the image rendered by the bean itself.

This blue area represents not only what the end user sees when the bean is used in a application builder, it represents the active area which will eventually responde to mouse down and mouse up events (added in subsequent example programs).

• Writing a Simple Bean
• Creating a Bean
• Adding Properties

		Questions? 27-Mar-97 Copyright © 1996,1997 Sun Microsystems Inc. All Rights Reserved.