Feature #102
Represent configuration in Java objects
| Status: | New | Start: | 02/07/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | Core | |||
| Target version: | 1.4.x branch |
Description
Create Java classes to represent the configuration items.
This should help structure the configuration, and is a first step for changing the configuration file format (see #18).
History
Updated by Jonathan Clarke about 1 year ago
- Tracker changed from Bug to Feature
Updated by Rémy-Christophe Schermesser 8 months ago
- Category set to Core
Updated by Rémy-Christophe Schermesser 8 months ago
It is very difficult to create configuration objects and having a dynamic mapping between the configuration file and the objects.
The reasons are :
- The configuration file is weird (eg : lsc.syncoptions.myTask and lsc.tasks.myTask, why not a lsc.tasks.myTasks.(whatever|syncoptions) )
- There is no complete description of the configurations files. The doc is there, but not in a single place
- Properties files are great but have limitation (try having a long lign of JS in your configuration)
So first of all, we should start thinking of a new way to write the configuration first, and then this feature will be easy to make
Updated by Sébastien Bahloul 2 months ago
- Target version changed from 1.3.x branch to 1.4.x branch
Retargeted