|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
The most obvious change to the RequestLog interface in Jetty was reverted (https://bugs.eclipse.org/bugs/show_bug.cgi?id=446564) in April 2015 but one more subtle change is that the RequestLog interface no longer extends (Jetty's) LifeCycle interface. As a result, any RequestLogImpl that get added as a handler to Jetty won't be started & configured by the container effectively rendering the log call a no-op.
I've opened a PR that addresses the problem here: https://github.com/qos-ch/logback/pull/269