Issue #158 has been updated by Sébastien Bahloul.
As I understand, this issue is related to the conception of synchronization : at this time, we have a source and a destination. I think one day, we should move to an event oriented model : data sources can are pushing modification events, and "engines" registered for these types of updates are consuming such events either to modify or to record in a blocking / non blocking way. ---------------------------------------- Bug #158: Logback & slf4j are not designed to output Object http://tools.lsc-project.org/issues/show/158 Author: Rémy-Christophe Schermesser Status: New Priority: Low Assigned to: Category: Core Target version: Sometime in the future When we used log4j, the CSV & LDIF output where made with the logger, but it was kind of a hack. Now woth logback & slf4j, you can not log anything more than Strings. So we should find a way to output CSV & LDIF in a "classic" way -- 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
