The class diagram in Figure 1 shows the main BeanView interface and the BeanViewHelper object. The BeanView interface is the main "contract" for an application developer, and the BeanViewHelper object has most of the reusable code for BeanView implementations.
The Property interfaces are mainly of interest for implementers of additional frameworks (for example, someone who wishes to add support for Wicket or JSF).

Figure 2: BeanView Underlying Models
Figure 2 shows the main models underlying the BeanView implementation. These models are used to bridge the various underlying data types with the models required by the implementation frameworks.

Figure 3: BeanView Implementations
Figure 3 shows the two main BeanView implementations as of this writing - the Swing and Echo 2.0 implementations.
@author $Author: wiverson $
@version $Revision: 1.1 $, $Date: 2006/02/01 06:11:06 $