All Packages from org.jfree.base.config.* to org.jfree.base.modules.*

Home >> All >> org >> jfree >> [ base Javadoc ]

•

• org.jfree.base: Javadoc index of package org.jfree.base.

Package Samples:

• org.jfree.base.config
• org.jfree.base.modules
• org.jfree.base.log

Classes:

• AbstractModule: The abstract module provides a default implementation of the module interface. The module can be specified in an external property file. The file name of this specification defaults to "module.properties". This file is no real property file, it follows a more complex rule set. Lines starting with '#' are considered comments. Section headers start at the beginning of the line, section properties are indented with at least one whitespace. The first section is always the module info and contains the basic module properties like name, version and a short description. module-info: name: xls-export-gui ...
• PackageManager: The PackageManager is used to load and configure the modules of JFreeReport. Modules are used to extend the basic capabilities of JFreeReport by providing a simple plugin-interface. Modules provide a simple capability to remove unneeded functionality from the JFreeReport system and to reduce the overall code size. The modularisation provides a very strict way of removing unnecessary dependencies beween the various packages. The package manager can be used to add new modules to the system or to check the existence and state of installed modules.
• PackageSorter: Compares two modules for order. A module is considered less than an other module if the module is a required module of the compared module. Modules are considered equal if they have no relation. When sorting, we match this modules position against all dependent modules until all positions are stable. Circular references are evil and are filtered during the module loading process in the package manager.
• AbstractBoot: The common base for all Boot classes. This initializes the subsystem and all dependent subsystems. Implementors of this class have to provide a public static getInstance() method which returns a singleton instance of the booter implementation. Further creation of Boot object should be prevented using protected or private constructors in that class, or proper initialzation cannot be guaranteed.
• ModuleInitializer: The module initializer is used to separate the initialization process from the module definition. An invalid classpath setup or an missing base module may throw an ClassCastException if the module class references this missing resource. Separating them is the best way to make sure that the classloader does not interrupt the module loading process.
• SubSystem: A sub-system holds a separate collection of modules. On a simple level, subsystems can be just libraries. Libraries offering services need a controlled way to initialize these services before dependent code starts using the library. This can be achived by embedding the library services into an own subsystem.
• Module: A module encapsulates optional functionality within a project. Modules can be used as an easy way to make projects more configurable. The module system provides a controled way to check dependencies and to initialize the modules in a controlled way.
• PadMessage: A message object that pads the output if the text is shorter than the given length. This is usefull when concating multiple messages, which should appear in a table like style.
• DefaultLogModule: The module definition for the System.out-Logging. This is the default log implementation and is provided to insert the logging initialisation in the module loading process.
• BootableProjectInfo: Project info for a bootable project. A bootable project provides a controlled way of initalizing all subsystems by providing a Boot loader implementation.
• ModuleInfo: The Module info class encapsulates metadata about a given module. It holds the list of dependencies and the module version and description.
• ModuleInitializeException: This exception is thrown when the module initialization encountered an unrecoverable error which prevents the module from being used.
• PackageState: The package state class is used by the package manager to keep track of the activation level of the installed or errornous packages.
• DefaultLog: A default log implementation. The Log class defines how to create Logger-contexts and how to forward messages to the logtargets.
• HierarchicalConfiguration: A hierarchical configuration. Such a configuration can have one or more parent configurations providing usefull default values.
• LogConfiguration: A log configuration class. This implementation is a simple frontend to the global configuration.
• Library: A simple class representing a library in a software project. Used in the AboutFrame class.
• PropertyFileConfiguration: A report configuration that reads its values from an arbitary property file.
• BaseBoot: The base boot class. This initializes the services provided by JCommon.
• DefaultModuleInfo: Provides a default implementation of the module info interface.
• MemoryUsageMessage: A helper class to print memory usage message if needed.
• SystemPropertyConfiguration: A property configuration based on system properties.

Home | Contact Us | Privacy Policy | Terms of Service