Issue #120 has been updated by Rémy-Christophe Schermesser.
Status changed from New to Feedback
In fact, you can already do that.
As we use properties files for configuration you can define a property :
my.constant = "OU=CLIENTS"
And then use it like this :
lsc.tasks.ldap2adUpdate.dn = \"cn=\" + srcBean.getAttributeValueById(\"cn\") +
\",\" + ${my.constant}
Can someone try this ?
I do not really know when Java is replacing the ${my.constant} by the real
value.
----------------------------------------
Feature #120: [Configuration] Allow user to define constants
http://tools.lsc-project.org/issues/show/120
Author: Thomas Chemineau
Status: Feedback
Priority: Normal
Assigned to:
Category: Core
Target version: 1.2 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
