JasperReportEngineConfigurationType (Complex Type)

Items

• reportType

  Flags: RAM,runtime,AVals:3

  Multiplicity: [0,1]

  Specifies type of the report.

• parent

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Indicates whether this report is a parent report or subreport. This item is specific to JasperRepors.

• subreport

  Flags: RAM,runtime

  Multiplicity: [0,-1]

  Reference to subreport. This item is specific to JasperRepors.

• template

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Report template. This is definition of base query, report structure and so on. This item is specific to JasperRepors. But it may be reused for other report types.

• templateStyle

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Report style template. This defines colors and similar look and feel properties. This item is specific to JasperRepors. But it may be reused for other report types.

• orientation

  Flags: RAM,runtime,AVals:2

  Multiplicity: [0,1]

  Report page orientation (portrait/landscape). This item is specific to JasperRepors. But it may be reused for other report types.

• export

  Flags: RAM,runtime,AVals:14

  Multiplicity: [0,1]

  Report output file format.

• useHibernateSession

  Flags: RAM,runtime

  Multiplicity: [0,1]

  This item is specific to JasperRepors.

• dataSource

  Flags: RAM,runtime

  Multiplicity: [0,1]

  This item is specific to JasperRepors.

• field

  Flags: RAM,runtime

  Multiplicity: [0,-1]

  Columns user definition. Name, type, report field, column name. This item is specific to JasperRepors.

• configuration

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Report configuration based on report configuration schema. TODO This element belongs to ReportType and should not be used elsewhere. This is a top-level element to make the implementation (JAXB marshal/unmarshal) easier.

• configurationSchema

  Flags: RAM,runtime

  Multiplicity: [0,1]

  This element contains the XSD-formatted definition of schema. The schema available in this definition is expected to comply to the usual midPoint schema structure (properties, property containers), although it should not contain objects (persistent objects identified by OID). Note: This schema is considered to be available only in run-time. Therefore code-generation methods such as JAXB cannot be applied here. Note: xsd:any is here, but maybe a stricter type would be preferable. However xsd:any seems to be a common practice (e.g. SPML, WSDL). TODO: rename to CachedSchemaType

• virtualizer

  Flags: RAM,runtime,oper

  Multiplicity: [0,1]

  Optional name of Jasper virtualizer class.

  This item is specific to JasperRepors.

• virtualizerKickOn

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Number of pages after Jasper virtualizer kicks on. This item is specific to JasperRepors.

• maxPages

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Number of pages after Jasper cancels report execution. This item is specific to JasperRepors.

• timeout

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Timeout in [ms] after Jasper cancels report execution. This item is specific to JasperRepors.