Many of the implementations of the API interfaces are singletons, usually services, which are instantiated by the Spring Framework. The Spring bean configuration files control how these singletons are created and configured, so it is important to understand the files before writing Java code that will run in JasperReports Server using the API.
The following is a brief overview of Spring 3.1.0 and is not meant to cover all the possible ways to configure Spring. For more information on Spring, refer to its reference documentation at http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/.
The Spring configuration files use XML to define Java singleton instances, called beans. In the JasperReports Server web application, these files are located under the WEB-INF directory. Their file names begin with applicationContext and end in .xml, for example, the file WEB-INF/applicationContext-adhoc.xml contains Ad Hoc-related beans:
| • | Each instance of a singleton is defined by a <bean> element. |
| • | Its type is specified by the class attribute. |
| • | Its reference ID is specified by the id attribute. |
| • | Properties of the instance are set with the <property> element:JasperReports Server |
| • | The name attribute corresponds to a Java property that follows JavaBean conventions. For example, a property with name abc should have a getter method getAbc() and a setter method setAbc(). |
| • | JasperReports ServerUsing the value attribute, properties can be set with a constant value. |
| • | Using the ref attribute, properties can be set with a reference to another bean. |
Below is part of a definition from a sample custom data source implementation. It demonstrates all of the conventions above; the original file is samples/customDataSource/webapp/WEB-INF/applicationContext-hibernateDS.xml in the JasperReports Server distribution.
To add your own instances to the server, you first need information about the specific enhancement that you want to implement. This determines the Java implementations that are required. A good example is creating a custom data source, which is documented in the JasperReports Server Administrator Guide. Samples of custom data sources are located in the JasperReports Server distribution under samples/customDataSource.
Once you have a Java class that you want instantiated along with JasperReports Server, you can deploy it by modifying the webapp directory as follows:
| • | Add your compiled Java class files to WEB-INF/classes, or create a JAR and add it to WEB-INF/lib. |
| • | Create a new Spring bean file under WEB-INF, using the naming convention described above. |
| • | Add a <bean> element for each object instance you want to create. |
| • | For each property you want to set, you must have a public setter and getter. |
| • | For each API implementation you want to access: |
| • | Add a setter and getter to your implementation whose types match the Java type of the API. |
| • | Find out the ID of the API instance you want; some IDs are listed in the table below. |
| • | Add a <property> element to your bean with a ref attribute whose value is the ID of the API instance. |
As an example of a reference to another bean, please refer to the factory property in the Spring file excerpt above. The CustomDataSourceDefinition instance uses the factory property to refer to a singleton implementation of CustomReportDataSourceServiceFactory, which has a bean ID of custom-DataSourceServiceFactory:
| • | The CustomDataSourceDefinition implementation defines a factory JavaBean property by implementing the following setter and getter: |
| • | public void setFactory(CustomReportDataSourceServiceFactory factory). |
| • | public CustomReportDataSourceServiceFactory getFactory(). |
| • | The <bean> element contains a <property> element with name set to factory and ref set to customDataSourceServiceFactory. |
The following table contains the APIs described in the rest of this section, along with their corresponding bean IDs and descriptions of their functions.
JasperReports Server Public Java API
API
Bean ID
Function
RepositoryService
Search, retrieve, and modify persistent objects in the repository.
EngineService
Run reports and handle report metadata.
ReportDataSourceService and ReportDataSourceServiceFactory
n/a
Implement data sources used for running reports and other purposes.
ReportSchedulingService
Manage report schedules.
UserAuthorityService
Manage internal users and roles.
OlapConnectionService
Manage OLAP-specific repository and model runtime.
OlapManagementService
Manage OLAP server run time.
ObjectPermissionService
Search, retrieve, and modify metadata repository object permissions.
Recommended Comments
There are no comments to display.