Issue #102 has been updated by Rémy-Christophe Schermesser.
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 ---------------------------------------- Feature #102: Represent configuration in Java objects http://tools.lsc-project.org/issues/show/102 Author: Jonathan Clarke Status: New Priority: Normal Assigned to: Category: Core Target version: 1.3 branch 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). -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
