The major issue I had was https://issues.apache.org/jira/browse/LOG4J2-31. We currently use SLF4J for audit logging via the SLF4J extension's EventLogger and EventData. Unfortunately, SLF4J has to convert the EventData object to XML since SLF4J/Logback don't provide a good way of handling this. To use this I had to create a Layout "wrapper" to convert the XML back to an EventData object so it could be used in various components. Needless to say this is cumbersome, slow and error prone.
The Log4J 2.0 API uses a Message interface for everything. This allows the caller to have much more control over the formatting of the objects without having to write complex layouts that check for the presence of certain types of objects as parameters (which they can still do of course). Ralph On Jul 29, 2011, at 2:51 AM, Gilles Sadowski wrote: > Hello. > >> I would have done that but some of the deficiencies are in the API and I >> couldn't get Ceki to incorporate them. > > Do you have a pointer to a listing of those deficiencies? > >> [...] > > > Thanks, > Gilles > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org >
