[GitHub] [logging-log4j2] rgoers commented on issue #1285: Identifiers, names, refs, nightmare docs, logging hell level 999

["rgoers (via GitHub)" <gi...@apache.org>]

rgoers commented on issue #1285:
URL: https://github.com/apache/logging-log4j2/issues/1285#issuecomment-1442024114

   The Log4j configuration is a tree structure organized as "Nodes" where a Node is nothing but a container of attributes and child Nodes. All the configuration dialects Log4j supports are converted into a Node tree. This works great for Yaml, JSON, and XML. Unfortunately, by their nature properties are not hierarchical. This means using properties is somewhat fitting a round peg in a square hole. For years Log4j didn't support properties due to this but we finally added it due to user's requests.  We have made slight "improvements" over time at user's requests but in the end I really don't think it makes it any simpler.
   
   I should note that the way Log4j 1 handled configuration was completely different. Properties were the original and only format. XML was bolted on after the fact and was basically a different configuration system from using properties.
   
   I, for one, highly encourage users to use a different one of the other formats.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org