logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <boa...@gmail.com>
Subject Re: Little help on reading and understanding the log4j2 source.
Date Thu, 10 Apr 2014 04:31:21 GMT
Spring is used in some web container tests (eg for a mock JNDI context).
The other property might actually just be unused at the moment.

On Tuesday, 8 April 2014, Nishantha Pradeep <mailtonishantha@gmail.com>
wrote:

> Came across another clarifications
>
> 1) log4j2.component.properties is mentioned in the code but I was not able
> to find such file in code base. Is it something supposed to be configured
> by end users ?
> 2) I have seen spring dependencies and what sort of functionality has
> spring been used for ?
>
> -Thanks
> Nishantha
>
>
> On Tue, Apr 8, 2014 at 10:41 AM, Matt Sicker <boards@gmail.com> wrote:
>
> The 1.2 api is for compatibility with code using the Log4j 1.2 library.
> It's a way to transition to 2.0. The other one is the main Log4j 2 API.
> log4j-core is the main implementation of said API.
>
> The log4j-osgi module is a parent project to several OSGi bundles that
> break up log4j-core into a few pieces along with the other main Maven
> modules (which could probably be simplified a bit). They're supposed to
> give modular JARs that work in an OSGi environment, but it's still a work
> in progress.
>
>
> On 8 April 2014 05:00, Nishantha Pradeep <mailtonishantha@gmail.com>wrote:
>
> Hi All
>
> Few things to clarify,
>
> 1) What is the difference between log4j-1.2-api and log4j-api modules.
>
> 2) What is the expectation of log4j-osgi module.
>
> -Thanks
> Nishantha
>
>
> On Tue, Apr 8, 2014 at 9:08 AM, Nishantha Pradeep <
> mailtonishantha@gmail.com> wrote:
>
> Working on it.
>
> Thanks
> Nishantha
>
>
> On Mon, Apr 7, 2014 at 9:06 PM, Matt Sicker <boards@gmail.com> wrote:
>
> 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.goers@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 <mailtonishantha@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-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
>
>
> --
> Matt Sicker <boards@gmail.com>
>
>
>
>
>
>
> --
> Matt Sicker <
>
>

-- 
Matt Sicker <boards@gmail.com>

Mime
View raw message