Configuration of a class

Because a class may have many members, that are not relevant for reporting, you need to configure a class before it can be used in a report.

The following items must be configured:

  1. Which members are made available for reporting.
  2. Element types of collections.

In addition you can specify:

  1. Better names that help the users for the classes.
  2. Simplification of the class model, by directly navigating object references.

This happens on the Members tab of the wizard.

  1. The left pane contains the members in your class. Only non-static methods that return a value and fields are shown. because Versant wraps fields in access methods during enhancement, fields are shown as methods. The member pointed to is an object reference. You can directly access the members of the referenced class. ReportWeaver will generate the necessary accss code transparently.
  2. A collection reference. You can addd it to your view just like other mebers, but you must specify the element type here, and you must edit the members of the view separately.
  3. This will add the selected members on the left to the view on the right.
  4. This will remove the selected members on the right from the view.
  5. This is the entry for a collection.(Indicated by the diamond shaped icon)
  6. For a collection entry, you must select the element type. Select the *Other to create a view on the fly for another class that is not listed here.
  7. This column shows the name of the member in your class.
  8. This column shows the name, that will be presented to the user.
  9. This shows the type of a class reference or a collection element.
  10. If the type is empty, then ReportWeaver assumes the basic java object type. Use the combo box to select one of your views as the class view.

Note: Any multi-valued class is called a collection. ReportWeaver treats the following classes as collections:

Class Configuration

  1. Here you can specify a different name for your class. This should be done if the original name is difficult to understand for the user.
  2. In an extension class, you can provide reporting specific functions, that are not available in your classes.
  3. Setting a class as default view speeds up the schema design process, because you do not need to define which view is used for a class reference.