n your example) are not processed, but simply
ignored. It would not be too hard to add a check which triggers a
warning if any unexpected keys are encountered.
Correctly.
When writing the configurator I did try to make it report all possible
configuration errors, and it is much better than it used
ed, but simply
ignored. It would not be too hard to add a check which triggers a
warning if any unexpected keys are encountered.
When writing the configurator I did try to make it report all possible
configuration errors, and it is much better than it used to be. But
this is still not handled. We c
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
Hi,
yesterday we had a problem with the configuration: getLogger returned a
logger with the configuration of the root-logger:
$logger = array(
'appenders' => array(
'default' => array(
'class' => 'LoggerAppenderFile',
'layout'
