Jump to: navigation, search

Difference between revisions of "BIRT Report Engine API"

Line 10: Line 10:
 
* [[Simple Execute]] - Simple RunAndRender Task Example
 
* [[Simple Execute]] - Simple RunAndRender Task Example
 
* [[Separate Run and Render]] - This example shows a running and then rendering the report.  It also illustrates getting the TOC from a rptdocument.
 
* [[Separate Run and Render]] - This example shows a running and then rendering the report.  It also illustrates getting the TOC from a rptdocument.
* [[Data Extract]] - Data Extract Task, used on a rptdocument.
+
* [[Data Extract]] - This example uses a Data Extract Task on a rptdocument.
 
* [[Parameter Details]] - This example displays parameter information retrieved from a report design.
 
* [[Parameter Details]] - This example displays parameter information retrieved from a report design.
* [[Servlet Example]] - This example demonstrate how to deploy the BIRT Engine within a servlet.
+
* [[Servlet Example]] - This example demonstrates how to deploy the BIRT Engine within a servlet.
 
* [[RCP Example]] - Explains deploying the BIRT Viewer within an RCP application
 
* [[RCP Example]] - Explains deploying the BIRT Viewer within an RCP application

Revision as of 00:27, 19 July 2006

BIRT Report Engine API Examples

Several examples of using the RE API are presented below. Please read the Report Engine API page to understand how the API works.

Add comments at the end of the example.


  • Simple Execute - Simple RunAndRender Task Example
  • Separate Run and Render - This example shows a running and then rendering the report. It also illustrates getting the TOC from a rptdocument.
  • Data Extract - This example uses a Data Extract Task on a rptdocument.
  • Parameter Details - This example displays parameter information retrieved from a report design.
  • Servlet Example - This example demonstrates how to deploy the BIRT Engine within a servlet.
  • RCP Example - Explains deploying the BIRT Viewer within an RCP application