Please make the LoggerContext of an AccessEvent accessible ---------------------------------------------------------- Key: LBACCESS-9 URL: http://jira.qos.ch/browse/LBACCESS-9 Project: logback-access Issue Type: New Feature Reporter: Joern Huxhorn Assignee: Logback dev list See http://qos.ch/pipermail/logback-dev/2009-March/003867.html I'd like to use the LoggerContext properties for filtering purposes. At the moment, both my Lilith multiplex-appenders contain support for an ApplicationIdentifier. In case of LoggingEvent, I changed the behavior of this property. It is now, if set, put into the properties of the LoggerContext. This isn't possible in case of AccessEvent because I can't access it's context, yet. The primary use of this property is ease of use while filtering events. While it would certainly be possible to deduce information about the logging application, it's easier and less error prone to simply use a manual identifier. My application identifier was a bit short-sighted so I'd like to just use any logger context properties for filtering. Thanks in advance, Joern. -- 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