Re: approach for defining loggers

What about event logging? < https://logging.apache.org/log4j/2.x/manual/eventlogging.html> This sounds pretty similar to what you're asking about. You define a map message essentially, plus your other requirements seem to be met here. On 17 October 2016 at 21:46, Gary Gregory

Re: porting log4j2 to .NET

Thanks for the guess. I assume there is enough "separate" big enough pieces that a small group of people could work on different sections without stepping on each others toes such that you'd get some linear scaling. For instance, it might take 3 people 2 months? Even if we double your

Re: porting log4j2 to .NET

Random guesstimate for a complete port, including tests (what about docs): 6 man-months. You can shorten things up by reducing appenders and configuration formats. Gary On Mon, Oct 17, 2016 at 5:33 PM, Nicholas Duane wrote: > Figured I would send this question out to the log4j

porting log4j2 to .NET

Figured I would send this question out to the log4j side. I have already had some email exchanges with the log4net mailing list regarding porting log4j2 to .NET. My suggestion was that the apache logging framework be a single architecture design which is platform agnostic and then teams which

Re: Log4j2 Kafka appender NullPointerException when put the related jars in tomcat lib

Ralph, are you going to work on this issue? On Mon, Oct 17, 2016 at 2:04 PM, Mikael Ståldal wrote: > So this issue is triggered by the fact that the Kafka client library we > use itself does logging via SLF4J during initialization. And in this > particular web

Re: Log4j2 Kafka appender NullPointerException when put the related jars in tomcat lib

So this issue is triggered by the fact that the Kafka client library we use itself does logging via SLF4J during initialization. And in this particular web configuration, org.slf4j.LoggerFactory.getLogger(Class) return null during Configuration.start(). On Sat, Aug 20, 2016 at 12:13 AM, Bill