Hi all, I think it all boils down to this. 1. If I need Log4j just as a logging utility and I need it FAST, a short cookbook would be of great help 2. Provided the powers of Log4j mentioned in the introduction, Where-To links would be of great help if I want to extend usage in future. So, I think we can stop further discussion on this and get back to implementing it :-) -Cheers Gautham
-----Original Message----- From: Mark Womack [mailto:[EMAIL PROTECTED]] Sent: Friday, April 12, 2002 9:46 AM To: 'Log4J Users List' Subject: RE: Help to configure Log4j with example Dave, if you have time to cook something up, go for it. I think you are on the right track. We can keep our toes out of harms way. Maybe people just haven't found Ceki's article and taken the time to read it. Maybe we need to redesign the layout of the web pages so folks can find things better, but I think your point about people approaching new stuff differently is valid. I know it took me some time to get my feet on the ground, so whatever we can do to help in this regard will potentially increase the adoption of log4j and the level of dicussion on the mailing list. thanks, -Mark > -----Original Message----- > From: Dave Bender [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 12, 2002 7:29 AM > To: Log4J Users List > Subject: RE: Help to configure Log4j with example > > > First, Ceki is right. There is a lot of good information in the short > manual. That article has a great introduction to logging generally and > nicely goes into detail about the major pieces of log4j. I > don't think it > needs to be broken up. > > But I also agree that first- and second-time users would > benefit by having > the how-to "recipe" to get started, with follow ups on each > of the major > areas, also in a cookbook style approach. I'd certainly be > willing to take a > stab at those if I'm not stepping on anyone's toes. > > Different people learn in different ways, so having a 'how to' recipe > approach as well as the short manual would serve log4j users well. > > I agree also that the how-to should end with a "where to go > from here..." > set of links. But I think the very next level would be just a > step beyond > the beginner stuff and make the write-your-own stuff a > subsequent level. So, > for example, the first how-to has among its "next steps" > links a link to a > document on Appenders and what they are and how to use the > existing ones. > That in turn could link to how to write your own Appenders. > > > Dave > > > -----Original Message----- > From: Ceki Gulcu [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 12, 2002 2:38 AM > To: Log4J Users List > Subject: RE: Help to configure Log4j with example > > > At 17:43 11.04.2002 -0700, you wrote: > > > Maybee the only thing we need is to break down the manual > > > into several htmls > > > with an index and have a section like "Getting started > for the really > > > impatient" or something of the kind. > > > What do you guys think: > > > >I think we should consider doing this. I do like the focus of Dave's > >document, ie "here's what you have to do to get up and > running, here is an > >extremely simple example, boom you're off". I would also > like to see a > >section like "where to go from here, frequently asked questions about > >extending log4j" that would cover writing custom appenders, levels, > filters, > >etc. Doesn't have to be detailed start to finish, but > points folks in the > >right direction. And a discussion about using xml > configuration files and > >the DOMConfigurator. Whatever we do now can be extended > over time, too. > >Maybe a faq on steroids is more the format? > > > >Ceki, do you mind if we use/break up your article as a source for the > >mini-manual? > > No, I don't mind. In any case, the short manual is licensed > under the Apache > Software License even if it it does not say so. (I'll add the license > information). > > On the other hand, wouldn't it be more useful if you made > your additions to > the > existing manual directly. Moreover, if you look at > > http://jakarta.apache.org/log4j/docs/documentation.html > > you will see that there are already a number of short > articles from third > parties. > My suggestion would be to work and improve the existing > manual rather than > starting a new effort. Or am I missing something here? > > -- > 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]> > -- 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]>
