ReportWeaver has some unique concepts to make it more productive and to enable reporting from object oriented data.
ReportWeaver uses an advanced algorithm to layout the element on the page. This enables ReportWeaver to optimize the layout when the contents of the page change. ReportWeaver is capable of dynamically adjusting the column sizes, so that the page space is used optimally. Altrnatively you can set fixed sizes for your columns and fields.
ReportWeaver also makes it easier to change a page. Whenever an element is dragged to a different location, ReportWeaver automatically moves the other elements out of the way. This is described in
detail in the chapter on
ReportWeaver uses a property sheet in its user interface where all settings of the edited elements are shown. Select the element to be modified and all its properties are shown. Most properties
are immediately editable. Details on the property sheet can be found in the
The schema representation of ReportWeaver is fully object oriented. It can therefore directly understand the data model of any object oriented data source like EJB Servers, Corba Servers, Object Databases, Object Oriented API etc. There is no need to map object structures to flat table structures. You will find, that using objects for reporting is much easier than relational tables. Objects offer more functionality which makes report design faster and more reliable.
Relational tables are mapped into this object model, to simplify reporting and to create an additional optimasation and security layer.
ReportWeaver organizes data in a hierarchical structure. This allows easy browsing of the data model. Each relationship appears as a branch in a tree. The data fields themselves are the leaves. A class is equivalent to the row type of a table. A one to one relationship is shown as a reference. A one to many relationship is shown as a collection in
|Opening/Saving a Repository in the Template Studio||Contents||Object Oriented Reporting versus Relational Database Reporting|