Thanks Nick.
I'll try that option as well.
Avi
On 11/28/2013 05:44 PM, Nick Williams wrote:
Avi, there is a simple solution to this:
What other components do (the tag library, the Commons adapter, and the JBoss Logging
project) is, when they create their wrapping logger, they make sure the
Avi, there is a simple solution to this:
What other components do (the tag library, the Commons adapter, and the JBoss
Logging project) is, when they create their wrapping logger, they make sure the
Log4j logger actually extends org.apache.logging.log4j.spi.AbstractLogger.
That's part of the co
I was actually considering extending the Log4JLogEvent, and overriding
the calcLocation method according to my needs, and setting my instance
of LogEventFactory which will return the extended Log4JLogEvent instead
of the original.
Makes sense?
Thanks.
Avi
On 11/27/2013 04:52 PM, Gary Gregor
Well, I think this would require either for you to compute the location
yourself, or, provide a patch to change Log4j to be able to parametrize it
and surface it to the API.
Gary
On Wed, Nov 27, 2013 at 9:48 AM, Avi Zohary wrote:
> Hey everyone.
>
> I'm looking into creating a logger framework
Hey everyone.
I'm looking into creating a logger framework that will use Log4J2 - I
need this for various reasons.
I know that in some cases, I will want the debug logs to include the
location data (what method and in what line the Logger.debug(...) method
was called).
The problem is, that
