I would agree on following the call path in the Logger classes. Start at the API section, then follow where that goes in the core implementation classes.
On 7 April 2014 07:08, Ralph Goers <ralph.go...@dslextreme.com> wrote: > If it was me I would start by looking at what happens when someone calls > Logger.info() or Logger.debug() and follow that code path. Starting from > LogManager is going to involve both creating a Logger as well as > initializing the whole framework, which will get quite complicated. > > Ralph > > > On Apr 7, 2014, at 12:01 AM, Nishantha Pradeep <mailtonishan...@gmail.com> > wrote: > > > Hi All > > > > I downloaded the log4j2 source and trying to read and and understand how > it works. I would be very thankful if someone could let me know a better > place to start reading the source. > > > > For example, the first lines of code of log4j2 executes. > > > > I thought the LogManager contains the first lines of code executes but I > feel that there is an initialization process before it. > > > > Thanks > > Nishantha > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > > -- Matt Sicker <boa...@gmail.com>
