Like all of our configurations, the JSON input is read as a tree of nodes. In
all of our configurations, first we grab all the attributes from the root node
- those represent the attributes on the Configuration node. Then all the
JSON/XML/YAML/Properties nodes are converted to configuration Node
On Jul 4, 2017 13:50, "Mikael Ståldal" wrote:
This is a bit strange from a JSON standpoint though, since the order of
properties in a JSON object is not supposed to be significant.
Agreed. What is the best way forward though?
Gary
On 2017-07-04 19:54, Ralph Goers wrote:
> This is not a bu
This is a bit strange from a JSON standpoint though, since the order of
properties in a JSON object is not supposed to be significant.
On 2017-07-04 19:54, Ralph Goers wrote:
This is not a bug but is intentional. Log4j processes configuration files from
beginning to end. It does not scan the
This is not a bug but is intentional. Log4j processes configuration files from
beginning to end. It does not scan the file twice as would be necessary if no
order was required. Properties MUST come first so that they can be used by the
configuration that follows. Because of that we will generate
Hi,
Opened PR in Github:
https://github.com/apache/logging-log4j2/pull/91
Thanks.
Regards,
Roman Sosnin
Backend Server Side Developer
Trusteer Security
IBM Israel Software Lab
From: Gary Gregory
To: Log4J Users List
Date: 20/06/2017 06:01
Subject:Re: Failing to initialize log