The significance of Bean in the builder name is that the class name provided to the builder follows a bean coding convention.
The convention follows a specific pattern. If the class has a float attribute called amount
, the class has a get method of the following style.
Optionally, the class has a set method of the following style.
public void setAmount(float newvalue)
This pattern of naming allows the builder during regeneration to introspect the class, determine the available attributes, and build up forms with those attributes.
Depending on the functionality chosen for the builder instance (to optionally generate or not generate view, delete, create, edit functions), this builder adds to the model and configures four Data Page builders, one for the table view, and three others for the view, create and edit functions. Because this builder depends on Data Page builder functionality, the Bean Master Detail output can be customized by adding Data Field Modifier builders and Data Column Modifier builders. And the Data Page validation mechanisms are available.
The attributes shown in the main collection are any of the following Java simple and object types for which a public get method is supplied: boolean, Boolean, byte, Byte, Character, double, Double, float, Float, int, Integer, long, Long, String.
Placement of the views on a page and the navigation (buttons and links) between views is configurable by overriding a set of default span tags that are listed in the builder. Also, because the generated Data Page objects are visible in the model, you can architect a custom flow if desired.
Parent topic: Bean Master Detail builder: wpf7