Re: Article Info

[Vikram Goyal]

Thanks for your comments and putting it on the site Ceki.

Rgs
Vikram

- Original Message -
From: "Ceki Gülcü" <[EMAIL PROTECTED]>
To: "Log4J Users List" <[EMAIL PROTECTED]>
Sent: Monday, August 26, 2002 10:47 PM
Subject: Re: Article Info


>
> Vikram,
>
> Here are my comments:
>
>Note that for the build to be successful, you will need to have the
>Java Management Extensions (JMX) API in your classpath, as well.
>
> JMX API is not required to build log4j.
>
>The signs indicate the ordering of the logging that log4j follows.
>
> No signs appear in the text.
>
>Open up config-simple.properties in a text editor. It contains three
>lines (besides comments). The first line, log4j.rootLogger=debug, R
>tells log4j that the level of the root logger is at DEBUG. This is the
>default and is not required. The value after the comma, R, is
>required. It tells log4j that the root logger has an appender attached
>to it and that the name of the appender is "R." The rest of the lines
>in this file tell log4j about the properties of this appender R.
>
> "R" is not the most descriptive name for a ConsoleAppender. In the
> following examples, appenders are also named as "R". Thus, there is a
> risk that the reader might be induced to believe that "R" is a name
> with magical properties.
>
>A note of warning, though, about using the JDBCAppender in the
>current version of log4j: the documentation says that it is going to
>be completely replaced in the future with a revamped version. Although
>the inner working of this appender might change, the way one goes
>about using it is unlikely to change.
>
> There is a strong chance that JDBCAppender will be re-written with
> fixed columns which will result in a simpler interface.
>
> In the JDBC example you do not provide instructions for configuring
> the database table. You should at least say that it is the reader's
> responsibility to configure the table.
>
>So what code changes are needed to start logging to the database now?
>None! That is where the enormous power of log4j really manifests
>itself. To start logging to the database, we don't need to make any
>code changes.
>
> Albeit the WEB-INF/web.xml file has to be modified.
>
> I enjoyed reading your article. It is written in an easy-to-read style
> and covers much ground in a short amount of space. Moreover, your sample
> web-application conveys useful information succinctly.
>
> The log4j website has been updated with a link to your article.
>
> At 00:14 13.08.2002 +1000, you wrote:
> >Hi All,
> >
> >I had put a link to a article I wrote on onjava.com.
> >(http://www.onjava.com/pub/a/onjava/2002/08/07/log4j.html) in an earlier
> >post.
> >
> >1. I would really appreciate if I could get some honest feedback. :) This
> >was my first article online and I just want to know whether to stop now
> >before its too late.
> >
> >2. How do I get about listing it on the log4j site? According to the info
on
> >the website, I just need to send a message to this list. Right ?
> >
> >Thanks for any answers/feedback.
> >
> >Regards,
> >Vikram
>
> --
> Ceki
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
>


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

Re: Article Info

[Ceki Gülcü]

Vikram,

Here are my comments:

   Note that for the build to be successful, you will need to have the
   Java Management Extensions (JMX) API in your classpath, as well.

JMX API is not required to build log4j.

   The signs indicate the ordering of the logging that log4j follows.

No signs appear in the text.

   Open up config-simple.properties in a text editor. It contains three
   lines (besides comments). The first line, log4j.rootLogger=debug, R
   tells log4j that the level of the root logger is at DEBUG. This is the
   default and is not required. The value after the comma, R, is
   required. It tells log4j that the root logger has an appender attached
   to it and that the name of the appender is "R." The rest of the lines
   in this file tell log4j about the properties of this appender R.

"R" is not the most descriptive name for a ConsoleAppender. In the
following examples, appenders are also named as "R". Thus, there is a
risk that the reader might be induced to believe that "R" is a name
with magical properties.

   A note of warning, though, about using the JDBCAppender in the
   current version of log4j: the documentation says that it is going to
   be completely replaced in the future with a revamped version. Although
   the inner working of this appender might change, the way one goes
   about using it is unlikely to change.

There is a strong chance that JDBCAppender will be re-written with
fixed columns which will result in a simpler interface.

In the JDBC example you do not provide instructions for configuring
the database table. You should at least say that it is the reader's
responsibility to configure the table.

   So what code changes are needed to start logging to the database now?
   None! That is where the enormous power of log4j really manifests
   itself. To start logging to the database, we don't need to make any
   code changes.

Albeit the WEB-INF/web.xml file has to be modified.

I enjoyed reading your article. It is written in an easy-to-read style
and covers much ground in a short amount of space. Moreover, your sample
web-application conveys useful information succinctly.

The log4j website has been updated with a link to your article.

At 00:14 13.08.2002 +1000, you wrote:
>Hi All,
>
>I had put a link to a article I wrote on onjava.com.
>(http://www.onjava.com/pub/a/onjava/2002/08/07/log4j.html) in an earlier
>post.
>
>1. I would really appreciate if I could get some honest feedback. :) This
>was my first article online and I just want to know whether to stop now
>before its too late.
>
>2. How do I get about listing it on the log4j site? According to the info on
>the website, I just need to send a message to this list. Right ?
>
>Thanks for any answers/feedback.
>
>Regards,
>Vikram

--
Ceki


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Article Info

[K. Mohan Nerella]

--- "Shapira, Yoav"
<[EMAIL PROTECTED]> wrote:
>
> >about the advantages Log4j has over the JDK
logging
> >package in this list is a must at the very
minimum.
> Of
> 
> I've found Ceki's (and other) documents on the
log4j
> web site comparing
> the two APIs to be fairly helpful.  Is there
> something not mentioned in
> there you'd like raised?  The articles there
could
> be updated.

hmmm, probably i am missing something. i just went to
the Log4j web site at
http://jakarta.apache.org/log4j/docs/documentation.html
but couldn't find any document comparing Log4j with
the JDK package. can you post the right URL.

the Log4j FAQ at
http://jakarta.apache.org/log4j/docs/FAQ.html has a
question about alternative logging packages which
doesn't seem to be working -
http://jakarta.apache.org/log4j/docs/FAQ.html#alternatives

Regards,
Mohan.

__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Article Info

[Shapira, Yoav]

Howdy,

>1.4. on first glance the JDK model seems to be so
>similar to what Log4j uses. i think that a discussion

The similarities go a lot deeper than a first glance.  They're very
intentional as well.  The intent is to make migrating trivial.

>about the advantages Log4j has over the JDK logging
>package in this list is a must at the very minimum. Of

I've found Ceki's (and other) documents on the log4j web site comparing
the two APIs to be fairly helpful.  Is there something not mentioned in
there you'd like raised?  The articles there could be updated.

Yoav Shapira
Millennium ChemInformatics


This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Article Info

[K. Mohan Nerella]

that is something going through the minds of lots of
developers who are just getting their hands into JDK
1.4. on first glance the JDK model seems to be so
similar to what Log4j uses. i think that a discussion
about the advantages Log4j has over the JDK logging
package in this list is a must at the very minimum. of
course the articles help too because they have a wider
audience.

Mohan.

--- Mark Womack <[EMAIL PROTECTED]> wrote:
>
> It is a good article and should be very helpful in
> getting people started in
> using log4j.  I would have spent some time on why
> log4j is better than the
> jdk logging package, as I sure that will be an early
> question for most
> developers trying to decide what package to use.
> 
> -Mark

__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Article Info

[Mark Womack]

Vikram,

> 2. How do I get about listing it on the log4j site? According 
> to the info on
> the website, I just need to send a message to this list. Right ?

Ceki is the one to update the main site with links, and he is on vacation
right now.  He can do it when he comes back.

It is a good article and should be very helpful in getting people started in
using log4j.  I would have spent some time on why log4j is better than the
jdk logging package, as I sure that will be an early question for most
developers trying to decide what package to use.

-Mark

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Article Info

[Vikram Goyal]

Thanks Doug.
If you have any questions about the article or the code, just shoot them off
to me.

Regards,
Vikram

- Original Message -
From: "Clifton, Doug" <[EMAIL PROTECTED]>
To: "Log4J Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, August 13, 2002 12:22 AM
Subject: Re: Article Info


> Vikram,
>   I read and downloaded the article this last weekend and I (as a newbie
> to log4j) found the information very useful.  I will know even more when
> I get some time to actually test the code and examples rather than just
> read about it.  It, however, has become a piece I saved off for later
> use.  Thanks for the information.
>
> Doug
>
>
>


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

Re: Article Info

[Vikram Goyal]

Instead, a clearer name such as stdout, generalLogFile, or
whatever should be used.

 >> Agreed and acknowledged.

a lot of people ask about where to put the config file, I would've
covered the default initialization procedure in more detail.

>> I deliberated on this for some time before deciding not to include it.
The reason for this was because of the excellent default initialization
procedure covered in >> the manual already. I had little that I could add on
top of it and therefore left it.

Keep writing ;)  If even one person finds it useful, than it's a good
service.  And we already had one reply saying the person found it
useful, so there are at least ten others who find it useful as well and
aren't (yet) on the list ;)

>> Good point and thanks for the encouragement.

Thanks and Regards,
Vikram


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Article Info

[Alan Yost]

Vikram - I must have missed the earlier posting.  I have just had a quick look and the 
section on "Tips and Tricks" is enough for me to give it a good rating.  Like everyone 
else on this list - I guess many of us are so caught up dealing with our own 
"distractions" that sometimes the feedback is a little delayed.  I endeavour to give 
the article a more thorough reading over the next few days and may then be able to 
provide more feedback.
 
Thanks for making the effort.
 
 
Al.

-Original Message- 
From: Vikram Goyal [mailto:[EMAIL PROTECTED]] 
Sent: Mon 12/08/2002 10:14 PM 
To: [EMAIL PROTECTED] 
Cc: 
Subject: Article Info



Hi All,

I had put a link to a article I wrote on onjava.com.
(http://www.onjava.com/pub/a/onjava/2002/08/07/log4j.html) in an earlier
post.

1. I would really appreciate if I could get some honest feedback. :) This
was my first article online and I just want to know whether to stop now
before its too late.

2. How do I get about listing it on the log4j site? According to the info on
the website, I just need to send a message to this list. Right ?

Thanks for any answers/feedback.

Regards,
Vikram


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 






winmail.dat
Description: application/ms-tnef

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Article Info

[Shapira, Yoav]

Hi Vikram,
First of all, thank you for writing the article.  All contributions are
welcome and it must have taken a chunk of time.

I like the section towards the end on NDC and MDC and their usage.  

The examples (code and configuration) throughout the article were
decent.  I would've advocate the use of an appender called R (or A, B,
R1, etc.).  Instead, a clearer name such as stdout, generalLogFile, or
whatever should be used.

More time could have been spent on initialization, both from a file and
programmatically.  Since the article assumed log4j and webapp usage, and
a lot of people ask about where to put the config file, I would've
covered the default initialization procedure in more detail.

>1. I would really appreciate if I could get some honest feedback. :)
This
>was my first article online and I just want to know whether to stop now
>before its too late.

Keep writing ;)  If even one person finds it useful, than it's a good
service.  And we already had one reply saying the person found it
useful, so there are at least ten others who find it useful as well and
aren't (yet) on the list ;)

>2. How do I get about listing it on the log4j site? According to the
info

I'm not sure.  I'd imagine Ceki is the judge on that.  However, and this
is not a knock on the article and is only IMHO, but I don't think it
offers a significant amount of additional knowledge not covered in the
site documentation already.  On the other hand, if we were to have a
central repository of anything ever written on log4j...  

Yoav Shapira
Millennium ChemInformatics

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Article Info

[Clifton, Doug]

Vikram,
  I read and downloaded the article this last weekend and I (as a newbie
to log4j) found the information very useful.  I will know even more when
I get some time to actually test the code and examples rather than just
read about it.  It, however, has become a piece I saved off for later
use.  Thanks for the information.

Doug 


Vikram Goyal wrote:
> 
> Hi All,
> 
> I had put a link to a article I wrote on onjava.com.
> (http://www.onjava.com/pub/a/onjava/2002/08/07/log4j.html) in an earlier
> post.
> 
> 1. I would really appreciate if I could get some honest feedback. :) This
> was my first article online and I just want to know whether to stop now
> before its too late.
> 
> 2. How do I get about listing it on the log4j site? According to the info on
> the website, I just need to send a message to this list. Right ?
> 
> Thanks for any answers/feedback.
> 
> Regards,
> Vikram
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: