Re: Failing to initialize log4j2 configuration dynamically

Feel free to take a look at the code. There a lot of other Jira issues that I think merit attention over this though, especially since I don’t consider it to be a problem. Ralph > On Jul 5, 2017, at 12:18 PM, Mikael Ståldal wrote: > > From a JSON standpoint, it would make

Re: Failing to initialize log4j2 configuration dynamically

I am all for it but cannot help on this particular issue. Gary On Jul 5, 2017 12:18, "Mikael Ståldal" wrote: > From a JSON standpoint, it would make sense to look up the nodes by name > and ignore the order. Should be fairly easy I guess? > > > On 2017-07-05 01:26, Ralph

Re: Failing to initialize log4j2 configuration dynamically

From a JSON standpoint, it would make sense to look up the nodes by name and ignore the order. Should be fairly easy I guess? On 2017-07-05 01:26, Ralph Goers wrote: 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

Re: Apache commons-logging bridge for log4j2

The ServiceLoader needs special handling to work in OSGi. See http://blog.osgi.org/2013/02/javautilserviceloader-in-osgi.html Ralph > On Jul 5, 2017, at 10:27 AM, Matt Sicker wrote: > > It's loaded via the

Re: Apache commons-logging bridge for log4j2

It's loaded via the ServiceLoader interface: https://github.com/apache/logging-log4j2/blob/master/log4j-jcl/src/main/resources/META-INF/services/org.apache.commons.logging.LogFactory On 5 July 2017 at 03:30, Asma Zinneera Jabir wrote: > I am trying to set up log4j2 for

Apache commons-logging bridge for log4j2

I am trying to set up log4j2 for Apache Commons Logging using the *commons-logging.properties* file in an OSGi environment. For Log4j 1 I could use org.apache.commons.logging.Log=org.apache.commons.logging.impl. Log4JLogger which maps to version Log4j 1.2. I couldn't find out the implementation