More about jConfig
This page contains a set of additional documentation that goes beyond the getting started documentation.
Using different parsers and configuration
In certain cases the XML structure of jConfig is just not enough or does not meet your requirements or expectations. There might be a lot of reasons. The latest versions supports different XML structures.The following types (or structures) are no supported:
- the default one (the good old one)
- nested categories
- cdata tags
More about variables
This page describes additonal features with variables: AdvancedVariablesThe event listener mechanism
jConfig supports the event-listener mechanism. The page PropertyListener describes it. There is also the FileListener that will notifya all listener when the configuration file has changed and will be reloaded.More about the handlers
The handlers are used to load a configuration file (or something else).There are a set of different handlers included which are explained here
Tracing errors
jConfig was designed in a way to not halt on any errors. For example if a configuration file is not found the ConfigurationManager will create a new one. Sometimes it would be helpfull to track down errors and so jConfig now includes an ErrorHandler.Including properties
Starting with version 2.7 it is now possible to include a properties file in any configuration. For example if you have a very few differences in your configuration in the test and production environment then this will definitely help you. Read more about hereInheritance
The version v2.8 offers the ability to extend a configuration. This means that a configuration extends another one and you have access to these properties as well. This is explain in ConfigurationInheritance.This extends the functionality of including properties described above to the next level.