Hi Gulliaume, That was useful. I was able to trace from:
Our Scala wrapper -> slf4j.Logger -> pax.Slf4jLogger -> TrackingLogger -> PaxLogger -> PaxLoggingService. I expected to find something like this somewhere: Thread.currentThread().getStackTrace()[2].getLineNumber() Where does the localization of the file/line/class actually occur in the call stack above? thanks! Adam On Mon, Feb 21, 2011 at 11:26 AM, Guillaume Nodet <[email protected]> wrote: > The slf4j binding is at the following location: > > https://github.com/ops4j/org.ops4j.pax.logging/blob/master/pax-logging-api/src/main/java/org/ops4j/pax/logging/slf4j/Slf4jLoggerFactory.java > > On Mon, Feb 21, 2011 at 16:51, Adam Crain <[email protected]> > wrote: > > Hello, > > I'm trying to trace how class/line number information gets from SLF4J > into > > pax logging and ultimately to log4j. Our system is in Scala, and we're > > using a trait to wrap slf4j, which works well, except for the fact that > we > > lose the line/class information because of the wrapper. > > https://github.com/ops4j/org.ops4j.pax.logging > > Any advice? Where is the actual pax logging binding for slf4j? > > thanks! > > Adam > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > -- *Adam Crain* Chief Platform Architect, GEC Office: 919.836.9916 Cell: 919.428.1002 [email protected] <[email protected]> *Green Energy Corp,* *enabling the smart grid of the future.** * *www.greenenergycorp.com* *www.totalgrid.org*
