[ 
http://jira.qos.ch/browse/LBACCESS-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11993#action_11993
 ] 

Joern Huxhorn commented on LBACCESS-12:
---------------------------------------

Ok, I've fixed it quick & dirty by extending AccessEvent and overwriting 
everything.

This issue isn't that important anymore but should probably be done at some 
point, anyway.

> 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

        
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev

Reply via email to