Using the Beans Development Kit 1.

September 1997
A Tutorial

Alden DeSoto

2550 Garcia Avenue

Mountain View, CA 94043 U.S.A.
408-343-1400
Sept 97
Contents

1. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Beans Development Kit (BDK) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Example Beans and Online Documentation . . . . . . . . . . . . . . . . 1-1
The BeanBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Testing Sample Beans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Creating and Testing the Simplest Bean . . . . . . . . . . . . . . . . . . . 1-5
Using the BeanBox to Create an Applet . . . . . . . . . . . . . . . . . . . 1-7
2. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Simple Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Indexed Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Bound Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Constrained Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Example Beans and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
3. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
WaterEventObject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

iii
 WaterSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Valve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Pipe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Testing WaterSource, Valve, and Pipe . . . . . . . . . . . . . . . . . . . . . 3-6
Example Beans and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
4. Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Customizer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
PropertyEditor Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
BeanInfo Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Example Beans and Customization . . . . . . . . . . . . . . . . . . . . . . . 4-3
5. Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
What to Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Changes and Versioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
6. Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
MANIFEST file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Additional Jar and Manifest File Information . . . . . . . . . . . . . . 6-2

iv JavaBeans Tutorial—September 1997

 Getting Started 1

JavaBeans is a portable, platform-independent software component model

written in Java. It enables developers to write reusable components once and
run them anywhere - benefiting from the platform-independent power of Java.

Beans are Java classes that can be manipulated in a visual builder tool and
composed together into applications. Any Java class that adheres to certain
property and event interface conventions can be a Bean. This short tutorial
provides simple examples of how to program to these conventions.

Beans Development Kit (BDK)

The Beans Development Kit (BDK) is a pure Java application whose only
dependency is the Java Development Kit (JDK) 1.1. The BDK provides support
for the JavaBeans APIs, a test container (the “BeanBox” to test Bean behavior),
sample Beans complete with their source code, the JavaBeans Specification, and
this Tutorial.

Example Beans and Online Documentation

Extensive online documentation for the sample Beans is available from
beans\doc\examples.html in the distribution. The online documentation is
an important complement to this book and provides descriptions, suggestions
for experimentation, and in some cases annotated code for each sample Bean.
The online documentation also provides information on the BeanBox.

1-1
 1

The BeanBox
The BeanBox is a sample container for testing Beans. The BeanBox handles
visible Beans, those Beans that have a visual element, and invisible Beans,
those Beans that are purely computational objects.

When you start the BeanBox, a ToolBox of sample Beans is displayed. Source
code for these Beans is provided in the demo\sunw\demo\ subdirectory of the
distribution.

Testing Sample Beans

Start the BeanBox with the following commands:

C:>cd beanbox
C:>nmake run

The BeanBox, ToolBox, and PropertySheet appear on the screen. To instantiate

a Bean in the BeanBox, click on the desired Bean in the ToolBox and then click
in the BeanBox area. In the example below, a Juggler and two OurButtons have
been instantiated in the BeanBox. The buttons have been labeled “Start” and
“Stop” by editing the label property in the PropertySheet.

save/load, cut/copy/paste, and

other operations supported via
File and Edit menus.

editable
sample properties for
Beans the selected
Bean in BeanBox

Icon
represen-
tations are
specified in
the .gmk
files of some
Beans
Beans instantiated
from ToolBox

1-2 JavaBeans Tutorial—September 1997

 1
To test the OurButton and Juggler sample Beans:

1. Instantiate two OurButtons and a Juggler in the BeanBox as shown above.

Label one button “start” and the other “stop” in the PropertySheet.

2. Select the “start” button.

Getting Started 1-3

 1
3. Select the Edit-->Events-->action-->actionPerformed pulldown menu as
shown above.
The BeanBox positions a line under your mouse arrow which you can use to
connect “start” to the Juggler.

4. Connect the line to the Juggler and click the mouse button.
The BeanBox responds with an Event Target Dialog as shown below. Juggler
methods which either take no argument or which take an argument of type
actionPerformed are listed in this dialog.

1-4 JavaBeans Tutorial—September 1997

 1
5. Select the start method and press “OK”.
The BeanBox will generate an adapter class. Once the BeanBox has
generated this code, press the “start” button in the BeanBox and the Juggler
will start juggling.

6. Connect the “stop” button to the Juggler stop method in the same
fashion.
Test by pressing the “stop” button.

Creating and Testing the Simplest Bean

1. Create a SimplestBean.java source file as shown below.
Create a simplest directory under demo\sunw\demo\ and create a
SimplestBean.java within it.

constructor package sunw.demo.simplest;

sets a visible
attribute import java.awt.*;

public class SimplestBean extends Canvas{

getMinimumSize
assures that Bean
will be big enough public SimplestBean(){
to see in BeanBox setBackground(Color.red);
}

public Dimension getMinimumSize(){

return new Dimension(50,50);
}

2. Create a SimplestBean.mk file as shown below.

Create this file in the demo\ directory. Refer to the sample Bean .mk files
provided in demo\ for additional examples.

Getting Started 1-5

 1
CLASSFILES= \
sunw\demo\simplest\SimplestBean.class

JARFILE= ..\jars\SimplestBean.jar

list of compiled .SUFFIXES: .java .class

class files
all: $(JARFILE)
Beans in
in this location will $(JARFILE): $(CLASSFILES) $(DATAFILES)
be found by the jar cfm $(JARFILE) <<manifest.tmp sunw\demo\simplest\*.class
BeanBox $(DATAFILES)
Name: sunw/demo/simplest/SimplestBean.class
Java-Bean: True
package classes <<
“Java-Bean: True” # Rule for compiling a normal .java file
causes class to {sunw\demo\simplest}.java{sunw\demo\simplest}.class :
appear in Toolbox
set CLASSPATH=.
javac $<

clean:
-del sunw\demo\simplest\SimplestBean.class
-del $(JARFILE)

3. Build the example

C:>nmake -f SimplestBean.mk

4. Run the BeanBox and create an instance of your SimplestBean.

Your simplestbean will automatically appear in the ToolBox at startup.

1-6 JavaBeans Tutorial—September 1997

 1

SimplestBean instance of
added to ToolBox SimplestBean
in the BeanBox

Using the BeanBox to Create an Applet

You can use the BeanBox’s File|MakeApplet... menu selection to create an
applet from the BeanBox contents. The resulting applet uses Java Object
Serialization to record the state of the Beans.

The File|MakeApplet... menu item creates a JAR file containing serialized data
and class files, a test HTML file that uses the JAR file (and any other JAR file
needed), a subdirectory with Java sources and makefile, and a readme file with
complete information about the generated applet and all files involved. This
generated readme file contains much useful information.

The generated applet can be used in any JDK 1.1-compliant browser. A good
test platform is the JDK 1.1 appletviewer (see http://java.sun.com/jdk/1.1/).
Another fully compliant browser is the HotJava browser (see http://
java.sun.com/products/hotjava). The preview2 Internet Explorer 4.0 release
does not yet support JAR files, and you will have to expand the JAR and
HTML files that are generated. A deserialization bug causes components to not
listen to mouse events also. See the generated readme file for more
information. The generated applet will not work in Netscape Communicator
versions 4.0 and 4.01; versions with full JDK 1.1 support are expected later this
year.

Getting Started 1-7

 1
Here’s a snapshot of the BeanBox’s File|Make Applet dialog:

To see how Make Applet works, instantiate the Juggler Bean and two buttons,
and connect them like you did at the beginning of this chapter.

1. The generated applet will have the same size as the BeanBox frame, so you
may want to start by adjusting the BeanBox size to the size of the applet you
want.

2. Choose File|Make Applet to bring up the above dialog. Use the default JAR
file and applet name for this example.

3. Press the OK button. You can inspect your handiwork by moving to the
beanbox/tmp/myApplet directory of your BDK installation.

4. Bring up appletviewer in the following way:

appletviewer <BDKInstallation>/beanbox/tmp/myApplet.html.
Here is what you should see:

1-8 JavaBeans Tutorial—September 1997

 1
Don’t forget to look at the generated myApplet_readme file, and the other
files generated.

Getting Started 1-9

 1

1-10 JavaBeans Tutorial—September 1997

 Properties 2

A property is a single public attribute. Properties can be read/write, read-only

or write-only. There are several types of properties: simple, indexed, bound,
and constrained.

Simple Properties
A simple property represents a single value and can be defined with a pair of
get/set methods. A property’s name is derived from the method names. For
example the method names setX and getX indicate a property named “X”. A
method name isX by convention indicates that “X” is a boolean property.

2-1
 2
public class alden2 extends Canvas {
property will String ourString="Hello";
be called
ourString public alden2(){
setBackground(Color.red);
setForeground(Color.blue);
}

“set” property public void setString(String newString){

ourString = newString;
}

“get” property public String getString() {

return ourString;
}

public Dimension getMinimumSize(){

return new Dimension(50,50);
}

Indexed Properties
An indexed property represents an array of values. Property element get/set
methods take an integer index parameter. The property may also support
getting and setting the entire array at once.

The BDK 1.0 BeanBox does not support indexed properties.

2-2 JavaBeans Tutorial—September 1997

 2

public class alden3 extends Canvas {

dataSet is an int[] dataSet={1,2,3,4,5,6};
indexed property
public alden3(){
setBackground(Color.red);
setForeground(Color.blue);
}

set entire array public void setDataSet(int[] x){

dataSet=x;
}

public void setDataSet(int index, int x) {

set one element dataSet[index]=x;
of array }

public int[] getDataSet() {

get entire array
return dataSet;
}

get one element public int getDataSet(int x) {

of array return dataSet[x];
}

public Dimension getMinimumSize(){

return new Dimension(50,50);
}
}

Bound Properties
A bound property notifies other objects when its value changes. Each time its
value is changed, the property fires a PropertyChange event which contains
the property name, old, and new values. Notification granularity is per bean,
not per property.

Properties 2-3
 2
public class alden5 extends Canvas {
String ourString="Hello";
declare and instantiate private PropertyChangeSupport changes =
a property change
object new PropertyChangeSupport(this);

public alden5()
{
setBackground(Color.red);
setForeground(Color.blue);
}

public void setString(String newString){

String oldString = ourString;
send change event to ourString = newString;
listeners when changes.firePropertyChange("string",oldString,newString);
property is changed }

public String getString() {

return ourString;
}

public Dimension getMinimumSize()

{
return new Dimension(50,50);
}

implement methods public void addPropertyChangeListener(PropertyChangeListener l) {

to add and remove changes.addPropertyChangeListener(l);
listeners. The BeanBox }
will call these methods
when a connection public void removePropertyChangeListener(
is made. PropertyChangeListener l) {
changes.removePropertyChangeListener(l);
}

You can test bound properties in the BeanBox as follows.

1. Instantiate a Bean with bound properties and any other Bean in the
Beanbox. Select the Bean with bound properties.

2. Select the Edit-->Events-->propertyChange-->propertyChange pulldown

menu as shown below.

2-4 JavaBeans Tutorial—September 1997

 2

3. Connect the Bean with bound properties to the second Bean and select a
target method.
The BeanBox will add the second bean to the bound property Bean’s list of
listeners.

4. When the BeanBox has finished generating code, change the bound
property value in the PropertySheet.
The selected method on the listener bean will be invoked.

Properties 2-5
 2

Constrained Properties
An object with constrained properties allows other objects to veto a
constrained property value change. Constrained property listeners can veto a
change by throwing a PropertyVetoException.

The JellyBean class in demo\sunw\demo\jelly\ has a constrained property

called PriceInCents.

public class JellyBean extends Canvas {

private PropertyChangeSupport changes =
new PropertyChangeSupport(this);
private VetoableChangeSupport vetos =
new VetoableChangeSupport(this);

......

set method throws a public void setPriceInCents(int newPriceInCents)

PropertyVetoException throws PropertyVetoException {
int oldPriceInCents = ourPriceInCents;
tell vetoers about the change; vetos.fireVetoableChange("priceInCents",
exception is not caught but new Integer(oldPriceInCents),
passed on to caller. new Integer(newPriceInCents));
ourPriceInCents = newPriceInCents;
change the property changes.firePropertyChange("priceInCents",
and send change event to new Integer(oldPriceInCents),
listeners
new Integer(newPriceInCents));
}

define methods to add and public

remove veto ers. void addVetoableChangeListener(VetoableChangeListener l) {
vetos.addVetoableChangeListener(l);
}

public
void removeVetoableChangeListener(VetoableChangeListener l) {
vetos.removeVetoableChangeListener(l);
}

......
}

In general, constrained properties should also be bound. As illustrated above

with PriceInCents, the source should notify any registered vetoableChange
listeners that a vetoableChange has been proposed. If the change is acceptable,

2-6 JavaBeans Tutorial—September 1997

 2
the source notifies any registered propertyChange listeners that the change has
completed. If any vetoable change listener rejects the change then a new
vetoableChange event will be delivered reverting to the previous value.

This allows a property watcher to either:

• treat constrained/bound property updates in a "two phase" fashion by
registering both a VetoableChangeListener and a PropertyChangeListener.
The watcher ignores the vetoableChange event unless it wants to veto the
change. At propertyChange event time it acts on the new value, as it knows
that this new value has successfully passed the vetoableChange phase.
• register only a vetoableChange listener. In this case, the watcher will be
notified about proposed changes and will also get subsequently notified if
the proposed change is vetoed. This approach means that the watcher is
deliberately choosing to assume that vetoable changes will "pass" and is
prepared to act on information that may be subsequently vetoed.

Example Beans and Properties

Several of the sample Beans illustrate properties. Refer to
beans\doc\examples.html.

Properties 2-7
 2

2-8 JavaBeans Tutorial—September 1997

Events 3

This chapter uses three example Beans to explain Events: WaterSource, Valve,
and Pipe. A WaterSource drips one WaterEventObject per second to its list of
WaterListeners. The list of WaterListeners may include any number and/or
combination of Valves and Pipes. An open Valve passes on WaterEventObjects
that it receives to its own list of WaterListeners. A closed Valve does not pass
on any WaterEventObjects. A Pipe behaves in the same way as an open Valve.

public interface WaterListener extends EventListener {

void handleSplash(WaterEventObject weo);
}

(implements)
WaterSource Valve (implements)
vector WaterListeners Pipe
vector WaterListeners
vector WaterListeners
(1 event per second)

WaterEventObject WaterEventObject

3-1
 3

WaterEventObject
public class WaterEventObject extends EventObject {
WaterListeners
check timeOfEvent long timeOfEvent;
to determine
whether it is more public WaterEventObject(Object o) {
than 2 seconds old. super(o);
timeOfEvent = System.currentTimeMillis();
}

public long getTimeOfEvent() {

return timeOfEvent;
}

WaterSource
public class WaterSource extends Canvas implements Runnable {

maintain a list of private Vector waterListeners = new Vector();

of objects which have Thread thread;
registered to recieve
water events public WaterSource() {
setBackground(Color.blue);
thread = new Thread(this);
thread.start();
}

public Dimension getMinimumSize()

{
return new Dimension(15,15);
}

public void run() {

while(true) {
splash();
try {
thread.sleep(1000);
} catch (Exception e) {}
}
}

3-2 JavaBeans Tutorial—September 1997

 3

BeanBox will call public synchronized void addWaterListener(WaterListener l) {

these methods to add
and remove registered waterListeners.addElement(l);
listeners }

public synchronized void removeWaterListener(WaterListener l) {

waterListeners.removeElement(l);
}
send a water event private void splash() {
to registered listeners Vector l;
WaterEventObject weo = new WaterEventObject(this);
you must copy the
vector before sending synchronized(this) {
the event in order to l = (Vector)waterListeners.clone();
avoid a timing race }

for (int i = 0; i < l.size(); i++) {

WaterListener wl = (WaterListener) l.elementAt(i);
wl.handleSplash(weo);
}
}

Valve
public class Valve extends Canvas implements WaterListener,
Runnable {

list of listeners private Vector waterListeners = new Vector();

last water event received private WaterEventObject lastWaterEvent;
open/close valve property private boolean open = true;
Thread thread;

public Valve() {
setBackground(Color.white);
thread = new Thread(this);
thread.start();
}

property get and set public boolean isOpen() {

methods return open;
}

public void setOpen(boolean x) {

open = x;
}

Events 3-3
 3

public Dimension getMinimumSize() {

return new Dimension(20,30);
}

this method is specified public void handleSplash(WaterEventObject e) {

in the WaterListener lastWaterEvent = e;
interface (which this class if (isOpen()) {
implements). setBackground(Color.blue);
repaint();
splash();
}
}

public void run() {

while(true) {
try {
thread.sleep(1000);
} catch (Exception e) {}

if (lastWaterEvent != null) {
make the valve white if long dt = System.currentTimeMillis() -
a WaterEventObject has lastWaterEvent.getTimeOfEvent();
not been recieved in the if ((dt > 2000) || (!isOpen())) {
last 2 seconds or if the setBackground(Color.white);
valve is closed repaint();
}
}
}
}
BeanBox will call these public synchronized void addWaterListener(WaterListener l) {
methods to add and waterListeners.addElement(l);
remove registered }
listeners
public synchronized void removeWaterListener(WaterListener l) {
waterListeners.removeElement(l);
}

void splash() {
send a water event to Vector l;
registered listeners
WaterEventObject weo = new WaterEventObject(this);
... method continued on
next page synchronized(this) {
l = (Vector)waterListeners.clone();
}

3-4 JavaBeans Tutorial—September 1997

 3

send a water event to for (int i = 0; i < l.size(); i++) {

registered listeners WaterListener wl = (WaterListener) l.elementAt(i);
wl.handleSplash(weo);
... method continued from
previous page }
}
}

Pipe
public class Pipe extends Canvas implements WaterListener,
Runnable {

list of listeners private Vector waterListeners = new Vector();

last water event received private WaterEventObject lastWaterEvent;
Thread thread;

public Pipe() {
setBackground(Color.white);
thread = new Thread(this);
thread.start();
}

public Dimension getMinimumSize() {

return new Dimension(150,10);
}

This method is specified public void handleSplash(WaterEventObject e) {

in the WaterListener lastWaterEvent = e;
interface (which this object setBackground(Color.blue);
implements) repaint();
splash();
}

public void run() {

while(true) {
try {
thread.sleep(1000);
} catch (Exception e) {}

if (lastWaterEvent != null) {
make the pipe white if long dt = System.currentTimeMillis() -
a water event has not lastWaterEvent.getTimeOfEvent();
been received in the if (dt > 2000) {
last 2 seconds setBackground(Color.white);
repaint();
}

Events 3-5
 3
}
}
}
public synchronized void addWaterListener(WaterListener l) {
BeanBox will call these waterListeners.addElement(l);
methods to add and }
remove registered
listeners
public synchronized void removeWaterListener(WaterListener l) {
waterListeners.removeElement(l);
}

void splash() {
WaterEventObject weo = new WaterEventObject(this);

for (int i = 0; i < waterListeners.size(); i++) {

WaterListener wl =
(WaterListener)waterListeners.elementAt(i);
wl.handleSplash(weo);
}
}
}

Testing WaterSource, Valve, and Pipe

1. Instantiate a collection of WaterSources, Valves, and Pipes in the BeanBox.

2. Select a WaterSource Bean and invoke the

Edit-->Events-->water-->handleSplash pulldown as shown in the picture
below.

3-6 JavaBeans Tutorial—September 1997

 3

3. Connect the WaterSource to a Pipe or Valve and select the handleSplash

method in the EventTargetDialog.
The BeanBox will generate an adaptor class.

4. Continue to connect water event producers to water event consumers as

desired.
You can manipulate the water flow by turning valves on and off as
illustrated in the example below.

Events 3-7
 3

Example Beans and Events

Several of the sample Beans illustrate events. Refer to
beans\doc\examples.html.

3-8 JavaBeans Tutorial—September 1997

 Customization 4

You can customize how a Bean appears and behaves within a builder
environment by using the Customizer, PropertyEditor, and BeanInfo interfaces
as described in this chapter.

Customizer Interface
Implement the java.beans.Customizer interface to provide your own GUI
implementation of the property sheet. For example, the OurButton bean in
demo\sunw\demo\buttons\ is packaged with a custom property sheet:

public OurButtonCustomizer extends Panel implements Customizer {

When implementing a custom property sheet such as OurButtonCustomizer, be

sure to implement addPropertyChangeListener and
removePropertyChangeListener. These will allow the BeanBox or other builder
environment to add property event listeners for the Bean as required.

4-1
 4

private PropertyChangeSupport support =

new PropertyChangeSupport(this);

public void addPropertyChangeListener(PropertyChangeListener l) {

support.addPropertyChangeListener(l)
}

public void
removePropertyChangeListener(PropertyChangeListener l){
support.removePropertyChangeListener(l)
}

PropertyEditor Interface
Implement the PropertyEditor interface to create a custom editor for a specific
property. The MoleculeNameEditor class in demo\sun\demo\molecule\ of
the distribution provides a good example of this.

If you provide a custom property editor class, you must refer to this class with
a call to PropertyDescriptor.setPropertyEditorClass in a BeanInfo
class (see next section).

PropertyEditorSupport public class MoleculeNameEditor

is a basic implementation extends java.beans.PropertyEditorSupport {
of the PropertyEditor
interface public String[] getTags() {
String result[] = {
"HyaluronicAcid",
"benzene",
"buckminsterfullerine",
"cyclohexane",
"ethane",
"water"};
return result;
}
}

BeanInfo Interface
Each Bean class may have a BeanInfo class which customizes how the Bean is
to appear in a builder. The BeanInfo can define properties, methods, events,
with display names and short help.

4-2 JavaBeans Tutorial—September 1997

 4
The example shown below is from MoleculeBeanInfo.java in
demo\sunw\demo\molecule\ of the distribution.

public class MoleculeBeanInfo extends SimpleBeanInfo {

SimpleBeanInfo
is a basic implementation
of the BeanInfo interface public PropertyDescriptor[] getPropertyDescriptors() {
try {
PropertyDescriptor pd = new PropertyDescriptor(
"moleculeName",Molecule.class);
Point to custom property
editor pd.setPropertyEditorClass(MoleculeNameEditor.class);
PropertyDescriptor result[] = { pd };
return result;
} catch (Exception ex) {
System.err.println("MoleculeBeanInfo:
unexpected exeption: " + ex);
return null;
}
}
}

The ExplicitButtonBean in demo\sunw\demo\buttons\also illustrates the use

of a BeanInfo class. ExplicitButtonBeanInfo defines four property descriptors,
rather than just one as in MoleculeBeanInfo. Note that properties are displayed
in the order they are listed in the PropertyDescriptor.

ExplicitButtonBean also illustrates the use of EventSetDescriptor and

BeanDescriptor. EventSetDescriptor allows you to specify the text labels used
in event dialogs and pulldowns. BeanDescriptor allows you to graphic image
files to represent the Bean.

Example Beans and Customization

Refer to beans\doc\examples.html for additional discussion of sample
Beans and customization.

Customization 4-3
 4

4-4 JavaBeans Tutorial—September 1997

 Persistence 5

To make fields in a Bean class persistent, simply define the class as

implementing java.io.Serializable.

public class Button implements java.io.Serializable {

}

The fields in any instance of a Bean which implements Serializable will

automatically be saved. You need do nothing else. You can prevent selected
fields from being saved by marking them transient or static; transient
and static variables are not saved.

What to Save
Generally, a Bean should store the state of any exposed properties. Selected
internal state variables may also be saved. Beans should not, however, store
pointers to external Beans.

Changes and Versioning

As you update software, you can add fields, add or remove references to
classes, change a field’s private/protected/public status without altering the
persistence schema of the class. However, deleting fields from the class,
changing a variable’s position in the class hierarchy, changing a field to or from
transient/static, or changing a field’s data type will change the persistence
schema.

5-1
 5
If you need to make changes to a class which alter its persistence, you might
define a version id field which can be checked at runtime. For example,

static final long SerialVersionUID 348749695999L;

5-2 JavaBeans Tutorial—September 1997

 Packaging 6

JavaBeans are distributed through JAR files. A JAR file is a ZIP format archive
file that may optionally have a MANIFEST file. The MANIFEST describes the
contents of the JAR file. A JAR file may contain .class files, serialized Beans
(.ser), help files in HTML format, and resources (images , audio, text).

MANIFEST file
If a JAR file does not have a MANIFEST, then all classes and serialized objects
in the package are treated as beans. Providing a MANIFEST file allows you to
specify which classes are Beans via "Java-Bean: True" entries (see Example
below).

Example
This example .mk file illustrates the compiling and packaging of three Beans
and two auxiliary classes. This .mk file was used to package the example
discussed in chapter 3, “Events”.

6-1
 6
CLASSFILES= \
sunw\demo\valves\WaterListener.class \
sunw\demo\valves\WaterSource.class \
sunw\demo\valves\Valve.class \
sunw\demo\valves\Pipe.class \
sunw\demo\valves\WaterEventObject.class

JARFILE= ..\jars\valves.jar

.SUFFIXES: .java .class

all: $(JARFILE)

# Create a JAR file with a suitable manifest.

$(JARFILE): $(CLASSFILES) $(GIFFILES)

jar cfm $(JARFILE) <<manifest.tmp sun\demo\valves\*.class $(GIFFILES)

Name: sunw/demo/valves/WaterListener.class
do not display
Java-Bean: False
in ToolBox
Name: sunw/demo/valves/WaterSource.class
Java-Bean: True

Name: sunw/demo/valves/Valve.class
Java-Bean: True

Name: sunw/demo/valves/Pipe.class
Java-Bean: True

do not display Name: sunw/demo/valves/WaterEventObject.class

in ToolBox Java-Bean: False
<<

# Rule for compiling a normal .java file

{sunw\demo\valves}.java{sun\demo\valves}.class :
set CLASSPATH=..\classes;.
javac $<

clean:
-del sunw\demo\valves\*.class
-del $(JARFILE)

Additional Jar and Manifest File Information

Refer to beans\doc\jar.html in the distribution for more information.

6-2 JavaBeans Tutorial—September 1997