You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-user@logging.apache.org by mgr Jan Obdrzalek <ob...@zoom-int.cz> on 2004/12/17 17:03:57 UTC

log4cxx - Default Initialization Procedure - is implemented somewhere?

On the page 
http://logging.apache.org/log4cxx/manual/Introduction.html#DefaultInitializationProcedure
is written some algorithm. I tryed to find implementation of it, but failed.

Is this algorithm implemented somewhere or am I supposed to write it myself in 
every program which uses log4cxxx?

(I can write it myself, but I would rather use standartized way, than 
reimplement it in not so professional way I did just now.)


-- 
Zdraví
      mgr. Jan Obdržálek
      obdrzalek@zoom-int.cz

      ZOOM International s.r.o., Perlová 1, 110 00 Praha 1, Česká republika

      telefon: 221 667 557, fax: 221 667 553, mobilní telefon: 737 239 887

      mailto:obdrzalek@zoom-int.cz, Internet: http://www.zoom-int.cz
      <http://www.zoom-int.cz/> 

       
      ZOOM is already for the 3rd year in a row on the top of fastest growing
      technological companies in Central Europe ranked by Delloite.

      http://www.fast50ce.com/new/?type=3&content=18#2
      <http://www.fast50ce.com/new/?type=3&content=18#2> 

Re: log4cxx - Default Initialization Procedure - is implemented somewhere? - SOLVED

Posted by mgr Jan Obdrzalek <ob...@zoom-int.cz>.
Problem was on my side.

I did use file called log4cxx.properties instead of  log4j.properties, so it 
was not found automagically and I got confused ... 
I renamed it to log4j.properties and all is OK now.

Thank you for help.

On Friday 17 December 2004 17:43, Curt Arnold wrote:
> On Dec 17, 2004, at 10:03 AM, mgr Jan Obdrzalek wrote:
> > On the page
> > http://logging.apache.org/log4cxx/manual/
> > Introduction.html#DefaultInitializationProcedure
> > is written some algorithm. I tryed to find implementation of it, but
> > failed.
> >
> > Is this algorithm implemented somewhere or am I supposed to write it
> > myself in
> > every program which uses log4cxxx?
> >
> > (I can write it myself, but I would rather use standartized way, than
> > reimplement it in not so professional way I did just now.)
>
> The algorithm is implemented in src/logmanager.cpp and has unit tests.
> The algorithm is described in detail so that you know what to expect
> when using default configuration and how to control its behavior.
> Generally, none of the environment variables would be set, so it would
> just look for log4j.properties in the current working directory.

-- 
Zdraví
      mgr. Jan Obdržálek
      obdrzalek@zoom-int.cz

      ZOOM International s.r.o., Perlová 1, 110 00 Praha 1, Česká republika

      telefon: 221 667 557, fax: 221 667 553, mobilní telefon: 737 239 887

      mailto:obdrzalek@zoom-int.cz, Internet: http://www.zoom-int.cz
      <http://www.zoom-int.cz/> 

       
      ZOOM is already for the 3rd year in a row on the top of fastest growing
      technological companies in Central Europe ranked by Delloite.

      http://www.fast50ce.com/new/?type=3&content=18#2
      <http://www.fast50ce.com/new/?type=3&content=18#2> 

Re: log4cxx - Default Initialization Procedure - is implemented somewhere?

Posted by Curt Arnold <ca...@apache.org>.
On Dec 17, 2004, at 10:03 AM, mgr Jan Obdrzalek wrote:

> On the page
> http://logging.apache.org/log4cxx/manual/ 
> Introduction.html#DefaultInitializationProcedure
> is written some algorithm. I tryed to find implementation of it, but  
> failed.
>
> Is this algorithm implemented somewhere or am I supposed to write it  
> myself in
> every program which uses log4cxxx?
>
> (I can write it myself, but I would rather use standartized way, than
> reimplement it in not so professional way I did just now.)
>

The algorithm is implemented in src/logmanager.cpp and has unit tests.   
The algorithm is described in detail so that you know what to expect  
when using default configuration and how to control its behavior.   
Generally, none of the environment variables would be set, so it would  
just look for log4j.properties in the current working directory.