1.3alpha-8 question

[Cheung, Quinn]

We are looking at using the latest version of Chainsaw (version 2.0) in one of 
our projects. I noticed that it requires log4J version 1.3. Why is this still 
in alpha version and is there a release date for the final 1.3 version?  Are 
there any problems or things I should know about given that it is an alpha 
version?  One of my coworkers thinks we should look at other options since 
alpha versions are often unstable and haven't had the problems worked out yet.

Thanks for any information you can provide,

Quinn Cheung
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Log4j xml configuration

[Drinkwater, GJ \(Glen\)]

Hi

I am currently moving all our log4j.properties files to XML files and
was wondering how I replicate this with the xml configuration.

In the properties file, I can put in 

log4j.logger.my.package=DEBUG

Which means only logs from 'my.package' with level DEBUG or above gets
logged and anything outside these package does not.

How do I do this with an XML configuration.

Thanks Glen

Re: Log4j xml configuration

[James Stauffer]

 
   
 


On 2/14/07, Drinkwater, GJ (Glen) <[EMAIL PROTECTED]> wrote:

Hi

I am currently moving all our log4j.properties files to XML files and
was wondering how I replicate this with the xml configuration.

In the properties file, I can put in

log4j.logger.my.package=DEBUG

Which means only logs from 'my.package' with level DEBUG or above gets
logged and anything outside these package does not.

How do I do this with an XML configuration.

Thanks Glen




--
James Staufferhttp://www.geocities.com/stauffer_james/
Are you good? Take the test at http://www.livingwaters.com/good/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

appender-ref to SMTPAppender knocks out log4j

[Eric Jain]

As soon as I uncomment "" in the example given 
below, log4j is no longer picked up (by commons-logging). Is there anything 
wrong with the configuration? There is no error message or warning!






http://jakarta.apache.org/log4j/";>

  


  


  

  






  


  

  

  

  



  




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

re: appender-ref to SMTPAppender knocks out log4j

[Wyss Patrick]

> As soon as I uncomment "" in the 
> example given 
> below, log4j is no longer picked up (by commons-logging). Is 
> there anything 

if it's working otherwise then make sure that you have all needed libraries in 
your classpath (mail.jar, activation.jar)

> wrong with the configuration? There is no error message or warning!

my guess is that you are running in some app-server, because log4j would 
otherwise log to System.err which you would have seen. check if System.out/err 
go into some app-server-log



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: appender-ref to SMTPAppender knocks out log4j

[Eric Jain]

Wyss Patrick wrote:

if it's working otherwise then make sure that you have all needed
libraries in your classpath (mail.jar, activation.jar)


I had these two jars in the web application, but not at the level of the 
application server (Jetty), which is where the log4j jar lives. After 
adding the two jars there, I got a javax.mail.NoSuchProviderException, 
which went away after removing the two jars from the web application...


Thanks!


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 1.3alpha-8 question

[Scott Deboy]

Chainsaw V2 has been available for over 3 years and is stable and
relatively bug free.  

Chainsaw V2's dependency on log4j 1.3 is that it stores logging event
information internally using the log4j 1.3 LoggingEvent class.  It also
provides a way to define 'receivers', which first became available in
log4j 1.3.

You can use log4j 1.2.x to send events to chainsaw (via socket appender,
xml or file appender).


Scott Deboy


-Original Message-
From: Cheung, Quinn [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 14, 2007 5:16 AM
To: log4j-user@logging.apache.org
Subject: 1.3alpha-8 question


We are looking at using the latest version of Chainsaw (version 2.0) in
one of our projects. I noticed that it requires log4J version 1.3. Why
is this still in alpha version and is there a release date for the final
1.3 version?  Are there any problems or things I should know about given
that it is an alpha version?  One of my coworkers thinks we should look
at other options since alpha versions are often unstable and haven't had
the problems worked out yet.

Thanks for any information you can provide,

Quinn Cheung
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 1.3alpha-8 question

[Scott Deboy]

Chainsaw V2 has been available for over 3 years, is stable and
relatively bug free.  

Chainsaw V2's dependency on log4j 1.3 is that it stores logging event
information internally using the log4j 1.3 LoggingEvent class.  It also
provides a way to define 'receivers', which first became available in
log4j 1.3.

Chainsaw V2 dependency on log4j 1.3 does not mean you have to use log4j
1.3 on the appender side - you can use log4j 1.2.x to send events to
Chainsaw via socket appender, xml or regular file appender.


Scott Deboy


-Original Message-
From: Cheung, Quinn [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 14, 2007 5:16 AM
To: log4j-user@logging.apache.org
Subject: 1.3alpha-8 question


We are looking at using the latest version of Chainsaw (version 2.0) in
one of our projects. I noticed that it requires log4J version 1.3. Why
is this still in alpha version and is there a release date for the final
1.3 version?  Are there any problems or things I should know about given
that it is an alpha version?  One of my coworkers thinks we should look
at other options since alpha versions are often unstable and haven't had
the problems worked out yet.

Thanks for any information you can provide,

Quinn Cheung
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

logger at method level

[Reshat Sabiq]

Do i understand correctly that the following will work just fine
log4j.logger.com.domain.paket.Klass.metod=DEBUG, CONSOLE, FILE2
as long as i construct the Logger w/
Logger.getLogger(Klass.class+".metod"); 

I might not actually use this, cause it sounds too convoluted, but it's a thing
i've been considering.

Thanks.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: logger at method level

[James Stauffer]

Try Logger.getLogger(Klass.class.getName() +".metod");  Besides that
it should work just fine.

On 2/14/07, Reshat Sabiq <[EMAIL PROTECTED]> wrote:

Do i understand correctly that the following will work just fine
log4j.logger.com.domain.paket.Klass.metod=DEBUG, CONSOLE, FILE2
as long as i construct the Logger w/
Logger.getLogger(Klass.class+".metod");

I might not actually use this, cause it sounds too convoluted, but it's a thing
i've been considering.

Thanks.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
James Staufferhttp://www.geocities.com/stauffer_james/
Are you good? Take the test at http://www.livingwaters.com/good/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Next alpha or nightly build?

[Curt Arnold]

On Feb 14, 2007, at 12:22 PM, Gary Gregory wrote:


Hello:

When can we get a new alpha build?
There are fixes we'd like to pick up.

Are there nightly builds somewhere?

Thank you.

Gary Gregory
Senior Software Engineer
Seagull Software
[EMAIL PROTECTED]
www.seagullsoftware.com



There are nightly builds produced by Gump, http://gump.apache.org,  
but the are explicitly disclaimed as being not ready for prime time  
and not reviewed.


Are you interested in the next log4j 1.2.x release or 1.3.x release?   
Both are overdue, but I can provide no estimate for a next release.   
A log4cxx release is long overdue and next on my to-do list.  At  
minimum the log4j sources need to be modified to conform to new  
Source Header and Copyright policy before a release can be prepared.


Any particular bug that you are interested in?  If it is one that is  
fixed on the 1.3 branch and not the 1.2 branch, would you be  
interested if it were back-ported?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Next alpha or nightly build?

[Gary Gregory]

> -Original Message-
> From: Curt Arnold [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 14, 2007 4:13 PM
> To: Log4J Users List
> Subject: Re: Next alpha or nightly build?
>
>
> On Feb 14, 2007, at 12:22 PM, Gary Gregory wrote:
>
> > Hello:
> >
> > When can we get a new alpha build?
> > There are fixes we'd like to pick up.
> >
> > Are there nightly builds somewhere?
> >
> > Thank you.
> >
> > Gary Gregory
> > Senior Software Engineer
> > Seagull Software
> > [EMAIL PROTECTED]
> > www.seagullsoftware.com
>
>
> There are nightly builds produced by Gump, http://gump.apache.org,
> but the are explicitly disclaimed as being not ready for prime time
> and not reviewed.
>
> Are you interested in the next log4j 1.2.x release or 1.3.x release?

We are only interested in 1.3. Only older releases of our product are based on 
1.2.x so we track newer releases there on an as need be basis.

> Both are overdue, but I can provide no estimate for a next release.
> A log4cxx release is long overdue and next on my to-do list.  At
> minimum the log4j sources need to be modified to conform to new
> Source Header and Copyright policy before a release can be prepared.
>
> Any particular bug that you are interested in?  If it is one that is
> fixed on the 1.3 branch and not the 1.2 branch, would you be
> interested if it were back-ported?

We are using 1.3alpha7 now. We cannot use 1.3alpha8 because of this bug:
http://issues.apache.org/bugzilla/show_bug.cgi?id=38993 (which is fixed)

We need to use the SMTPAppender with a user name and password. The SMTPAppender 
user name and password are in 1.2, not in 1.3alpha7, and in SVN trunk.

So we need a 1.3 alpha release that fixes 38993 and has the SMTPAppender user 
name and password.

Gary

>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]