Many of the attributes for the UI components and properties for the managed beans need to be set to instances of property classes. To illustrate how to use these property classes in an application, consider the following example.
The Logon
component has an attribute called logonButton
. That attribute must be set to an instance of the SubmitButton
class, which contains the properties that define the look and behavior of the button for the logon form. To access and manipulate these properties, the Logon
component must reference a bean that instantiates the SubmitButton
class. You must first create the Java bean.
Tip: Alternatively, you can right
logonButton1
.SubmitButtonProps
class:com.businessobjects.jsf.sdk.properties.SubmitButtonProps
Tip: Alternatively, you may search for a class to add by clicking on the button next to the Class field. A Class Selection dialog box will appear where you can perform an alphabetized search for a valid class by typing the beginning portion of the class name in the Choose a class field.
SubmitButton
class.All available SubmitButton class properties that you can choose from are displayed in the list In this case, you will see properties such as text
, imageUrl
, type
, alignment
, and visible
.
For example, if you select the text
property, enter the string that you want to appear on the logon button, such as "Log on", or "Submit".
A Java bean called logonButton1
is added to the page and made visible in the Page Data view. Next, add a reference to this bean from the Logon
component.
Logon
component in the visual designer.logonButton
attribute.The formatting and behavior of the Logon
component's logon button will now be governed by the data in the newly created bean. The bean can be further configured and its property values changed within the Page Data view. All component attributes that require property classes function this way.
In addition, the EnterpriseItems
and Identity
beans contain properties that must be configured for property classes. A reference to a property bean can be added similar to the way components are added, by initializing the EnterpriseItem
or Identity
bean's property from the Page Data view. For details, see How do I initialize the default values of Java beans?.
A list of the component attributes and managed bean properties that require property classes is shown in the following tables.
Note: For detailed documentation on the property classes, see the Crystal Reports for Rational Application Developer Java API Reference.
UI Component | Attribute | Property Class |
---|---|---|
Managed Bean | Property | Property Class |
---|---|---|
Business Objects http://www.businessobjects.com/ Support services http://www.businessobjects.com/services/support/ |