Issue #265 has been updated by Sébastien Bahloul. Status changed from Resolved to Closed
This issue won't be fixed on the 1.3 branch and does not apply to the 2.0 ---------------------------------------- Bug #265: New requestNameForNextId property seems to be mandatory http://tools.lsc-project.org/issues/265 Author: Frederic Soulier Status: Closed Priority: Normal Assigned to: Sébastien Bahloul Category: Core Target version: 1.3.0 Problem in version: Using LSC with the last trunk version cause the following message if the property "requestNameForNextId" is not set in lsc.properties file : <code> Caused by: java.lang.RuntimeException: No requestNameForNextId property specified in org.lsc.service.SimpleJdbcSrcService. Aborting </code> This new property should not be mandatory -- 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
