Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Thu, 17 Apr 2014 21:17:16 +0000 (UTC)
From: "Ralph Goers (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12708912.1397682572126.135095.1397769436142@arcas>
In-Reply-To: <JIRA.12708912.1397682572126@arcas>
References: <JIRA.12708912.1397682572126@arcas>
Subject: [jira] [Comment Edited] (LOG4J2-607) log4j2 json files do not
 support property substitutions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973358#comment-13973358 ] 

Ralph Goers edited comment on LOG4J2-607 at 4/17/14 9:16 PM:
-------------------------------------------------------------

The error with not having the properties at the time the top level attributes are parsed was fixed, so I don't know why it would now not be working. The Interpolator always has system properties available, which is what that unit test uses.

Did the addition of InitialLoggerContext cause Log4j to initialize before the system property is set?


was (Author: ralph.goers@dslextreme.com):
The error with not having the properties at the time the top level attributes are parsed was fixed, so I don't know why it would now not be working. The Interpolator always has system properties available, which is what that unit test uses.

> log4j2 json files do not support property substitutions
> -------------------------------------------------------
>
>                 Key: LOG4J2-607
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-607
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.0-rc1, 2.0-rc2
>         Environment: Windows 7, JVM 7, Tomcat 7. Also tested using Mac OS X and JVM 8 (Tomcat 7).
>            Reporter: Sebastian Audet
>            Assignee: Matt Sicker
>         Attachments: log4j2.json
>
>
> Using Property substitution in the latest release candidate doesn't work in JSON configuration files.
> Seems to work fine in XML files though - suggest actually parsing the results of the JSON file configurations?


--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org