See: Description
Interface | Description |
---|---|
DataFactoryReadHandler |
Creation-Date: Jan 15, 2007, 6:51:41 PM
|
PasswordEncryptionServiceProvider | |
ReportElementReadHandler |
Creation-Date: Dec 18, 2006, 1:06:08 PM
|
SubReportReadHandler |
Creation-Date: Dec 18, 2006, 1:03:58 PM
|
Class | Description |
---|---|
ClassicEngineFactoryParameters |
Container class for the resource key factory parameters that the reporting engine has knowledge of.
|
CrosstabXmlResourceFactory | |
DataFactoryReadHandlerFactory | |
DataFactoryXmlResourceFactory | |
GroupList | Deprecated
The group-list is a legacy class and should not be used outside the legacy handling.
|
MasterReportXmlResourceFactory | |
Obscurificate48PasswordEncryptionServiceProvider | |
ObscurificatePasswordEncryptionServiceProvider | |
ParserBaseModule |
The module definition for the parser base classes module.
|
PasswordEncryptionService | |
PlainTextPasswordEncryptionServiceProvider | |
PropertyAttributes | |
ReportElementReadHandlerFactory | |
ReportGenerator | Deprecated
Use LibLoader directly.
|
ReportParserUtil |
A helper class to make parsing the xml files a lot easier.
|
ReportResource |
A resource implementation that tries to clone the provided parse-result so that the cached object is shielded from
later modifications.
|
StaticAESPasswordEncryptionServiceProvider |
If you use dependency injection to provide your own key make sure that you also redefine the prefix.
|
SubReportReadHandlerFactory |
Creation-Date: Dec 18, 2006, 1:05:00 PM
|
SubReportXmlResourceFactory |
At the moment two report definition formats are supported, the simple profile is a simplified model of the report definition. Although it does not support all advanced features, its simple structure helps to understand the basic report process and makes it possible to easily write report definitions.
The second parser uses a more complex model, which describes the report is a very detailed way. Due to the low level orientation of the report definition format, writing report definition is more complicated and requires detailed knowledge of the object structures used in JFreeReport. Its more generalized structure allows to define every aspect of the report definition and makes it possible to use all implemented features of JFreeReport.