Am 09.02.2012 22:33, schrieb Ivan Habunek:
On 9 February 2012 22:21, Florian Semm wrote:
but in my example the configuration was wrong and nothing went wrong. We're
wondering why the hell is our logger not writing anything in this log-file.
I have no good idea to solve the problem/case, without
On 9 February 2012 22:21, Florian Semm wrote:
> but in my example the configuration was wrong and nothing went wrong. We're
> wondering why the hell is our logger not writing anything in this log-file.
> I have no good idea to solve the problem/case, without breaking the
> inheritance.
Aha, I see
Am 09.02.2012 17:49, schrieb Ivan Habunek:
On 9 February 2012 08:40, Florian Semm wrote:
We have forgot the option 'logger' under 'rootLogger'. It is maybe better to
trigger a notice 'you have called an unkown logger', than to return a logger
with the configuration of the root-logger. To locate
On 9 February 2012 08:40, Florian Semm wrote:
> We have forgot the option 'logger' under 'rootLogger'. It is maybe better to
> trigger a notice 'you have called an unkown logger', than to return a logger
> with the configuration of the root-logger. To locate the error would be much
> easier.
This
On Thu, Feb 9, 2012 at 8:40 AM, Florian Semm wrote:
> Hi,
>
> yesterday we had a problem with the configuration: getLogger returned a
> logger with the configuration of the root-logger:
...
> We have forgot the option 'logger' under 'rootLogger'. It is maybe better to
> trigger a notice 'you have
