Issue #120 has been updated by Sébastien Bahloul.
It can be achieved in 1.2 (and probably in 1.3) by using custom library binding
:
lsc.tasks.FirstTask.customLibrary = org.lsc.Configuration
Put a setting like the following inside lsc.properties :
entity = CORP
Then you can use the getString method to get a specific value in force / create
value, for example :
lsc.syncoptions.FirstTask.o.force_value = custom.getString("entity");
----------------------------------------
Feature #120: [Configuration] Allow user to define constants
http://tools.lsc-project.org/issues/120
Author: Thomas Chemineau
Status: Assigned
Priority: Normal
Assigned to: Rémy-Christophe Schermesser
Category: Core
Target version: 1.4.x branch
It could be very useful to allow user defining constants. It could be
implemented as properties that could be reuse in other LSC properties.
For example, if I define:
lsc.constants.ouToSync = "OU=CLIENTS"
Then I would like to reuse it as the following:
lsc.tasks.ldap2adUpdate.dn = \"cn=\" + srcBean.getAttributeValueById(\"cn\") +
\",\" + lsc.constants.ouToSync
--
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
