Bug #158
Logback & slf4j are not designed to output Object
| Status: | New | Start: | 30/11/2009 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | Core | |||
| Target version: | Sometime in the future | |||
| Problem in version: |
Description
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
History
Updated by Sébastien Bahloul 7 months ago
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.