Also another logging-related problem that I sometimes have is that if an ajax
call throws an exception, nothing is shown in the container logs. I can only
see the stacktrace when I open up the ajax call's response in firebug. This
sometimes takes time to figure out as at first it seems that clic
+1
On Jan 27, 11:59 pm, Jeppe Nejsum Madsen wrote:
> Hi,
>
> I was thinking about some improvements to Lift's logging code:
>
> 1) Make the slf4j logging configurable in the same way as log4j (ie with
> dev, prod logback files)
>
> 2) Add support for MDC to Lift's logging interface (and the log4j
aw writes:
> One thing that bugs me is how all the logging comes from one logger:
> lift [Slf4jLogger.scala:110]
> As a result, you don't have the granularity to adjust just
> org.liftweb.http or org.liftweb.mapper, for example.
Indeed. That is one of the things I would try to remedy
http://git
One thing that bugs me is how all the logging comes from one logger:
lift [Slf4jLogger.scala:110]
As a result, you don't have the granularity to adjust just
org.liftweb.http or org.liftweb.mapper, for example.
I liked your suggestion about adding a Logging trait:
http://groups.google.com/group/lif
