[ http://jira.qos.ch/browse/LBACCESS-12?page=com.atlassian.jira.plugin.system.... ] Joern Huxhorn commented on LBACCESS-12: --------------------------------------- Well, yes, I think I could give it a go. Fortunately, I was able to just put nulls into the c'tor for now and nothing exploded since the arguments are evaluated lazily. My current solution looks like this: https://github.com/huxi/lilith/blob/master/lilith/src/main/java/de/huxhorn/l... (see AccessEventFoo class) Much more important for me is a fix for LBCLASSIC-257 right now since it prevents 100% formatting support at the moment. I can't use a similar "hack" in that case since the argument is evaluated immediately.
Please add IAccessEvent (and AccessEventVO) similar to the LoggingEvent counterparts ------------------------------------------------------------------------------------
Key: LBACCESS-12 URL: http://jira.qos.ch/browse/LBACCESS-12 Project: logback-access Issue Type: Improvement Affects Versions: 0.9.20 Reporter: Joern Huxhorn Assignee: Logback dev list
I'm currently implementing "cat" functionality for Lilith data files, i.e. events stored in Lilith data files can be printed using ch.qos.logback.classic.PatternLayout and ch.qos.logback.access.PatternLayout. This works for LoggingEvent since I could implement a iLoggingEvent wrapper for my own LoggingEvent. It does not work for AccessEvent, though, because there is no IAccessEvent interface and I can't instantiate AccessEvent and set the properties manually. ch.qos.logback.access.PatternLayout is currently working on an AccessEvent and I'd like to use it's functionality.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira