Home >> All >> jbreport >> [ data Javadoc ]

• jbreport.data: Javadoc index of package jbreport.data.


Package Samples:

• jbreport.data

Classes:

• QueryResult: This interface is meant as a thin wrapper over classes like resultsets. This is done so that we can perform actions such as aggregations without having to re-implement a monster interface... Having implemented java.sql.ResultSet before, believe me, it is no fun. This interface should provide for a class to register itself, and be called on certain actions. This is done with the registerBreakListener(jbreport.util.BreakEventListener, jbreport.util.ReportBreak) 55 method As a report does not require fancy tricks like scrolling backwards over the dataset, we only have a next() method for iteration. ...
• Datasource: This represents a source of data. It is used in association with the Query class to obtain data which is then used in rendering the report. Internally, this uses the State (GOF p305) pattern, where the state is the type of datasource that is created. When an instance of this class is created, there is no useable state, and the application should set the type of datasource, and any properties that are applicable. This is then used to create the correct physical datasource connection. There are two currently available datasource types, namely, JDBC and class factory (java).
• PhysicalConnection: This interface defines the contract that is required for the class to be pluggable into a Datasource instance. Any classes implementing this method should have a public no-args constructor which can be used by the datasource.
• Aggregate: This performs operations on groups of data in the report, all of which are strongly typed. It provides an extensible interface whereby operations can be defined for Aggregates to perform.
• Query: This provides for a named query to be captured from an xml definition. It is executed against a predefined datasource.
• RegisteredBreak: This is used to provide easy access to BreakEventListener's and their associated ReportBreak validators.
• AbstractQueryResult: This helper class is designed to make it easier for applications to define a concrete QueryResult class.
• ResultSetAdapter: This is an adapter for a ResultSet to make it compatible for the QueryResult interface.
• JavaPhysicalConnection: This is used to extract a database connection from an existing application connection.
• JDBCPhysicalConnection: This is used to create a new connection to a JDBC database.
• AggregatableSum: The summing Aggregatable class.

Home | Contact Us | Privacy Policy | Terms of Service