
|
File Archiving ServiceThis plugin provides a service to store and retrieve files on disk. It encapsulates file access to J2EE applications so they don't have to manually deal with locating the Geronimo installation directory and manipulating java.io.File objects. Future plans for this plugin include dealing with file handle limits and scheduling saved files to be deleted at a certain time. Last updated on 10/11/2006
JasperReports DeployerWith this plugin, JasperReports report templates may be bundled into a JAR or packaged in web application or EJB JAR, and a special report deployment plan lists the report template files along with associated database connection pools, default report criteria, archiving settings, etc. Once a report definition is deployed (either standalone or included in a J2EE module), applications can generate a report simply by invoking the Report Manager with the name of the report and the criteria (if any) necessary to execute it. If reports are deployed standalone, the template files should be packaged into a JAR and the JAR and deployment plan can be passed as arguments to the normal Geronimo deploy tool, console deploy screen, etc. If reports are deployed in a J2EE module, the templates should be included on the class path (e.g. in WEB-INF/classes) and the report deployment plan should be packaged into the WAR or EJB JAR at META-INF/geronimo-jasper.xml Note that the report templates always use the standard JasperReports syntax; The deployment plan is a separate XML file that links each report template to other related settings for Geronimo. Last updated on 10/11/2006
JasperReports IntegrationThis plugin provides a report manager service, with which report definitions can be registered and reports can be generated, archived, and retrieved. You can associate a JasperReports report template with a database pool deployed in Geronimo, provide default report criteria, specify allowed output formats (PDF, HTML, RTF, Excel, etc.), and control archiving settings. With this plugin alone, an application must manually register report definitions with the report manager during deployment and manually unregister the report definition during undeployment (usually e.g. with a servlet context listener). With the related JasperReports Deployer plugin, reports can be automatically deployed either standalone or as part of a J2EE application module. Last updated on 10/11/2006
|
