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 <[email protected]> wrote: > 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 if I wrap the Log4J2's logger, the location will > always show the wrapping class's call to the logger, as the location. > > I read here ( http://logging.apache.org/log4j/2.x/manual/layouts.html# > LocationInformation) that to get the location information, the Log4J2 > logger will take a stack and walk a certain depth in it to find the caller. > > Is it possible to make Log4J2 change that depth so it will find the method > that called my wrapper class instead of finding my wrapper class? > > -- > Thanks > Avi Zohary > > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
