Hexsel, Gustavo wrote:
That helps!
Whooooh. Good! I was a little worried people would say "This stinks! I'm more confused than ever!!!"...And then I would have to go back to the drawing board again. :-)
A few suggestions for the tomcat deployment: - make using log4j easier (either offer a binary version of tomcat-juli.jar that uses log4j - no source required since I can't build locally due to some dbcp error; alternatively it could use common-logging's autodetect, if log4j is available on the path, use it...)
I would go after Log4J in the tutorial, but to be honest I did not really see any killer use cases for it. Also, for people just trying to figure out logging, it's much easier to start with what's already there, get very comfortable with that, and then attempt the log4j switcho in the event that there is a use case X that they just have to have. Do you have by chance? I could add a "Why you should consider log4j section...".
- adapt the main log4j formatter (I'll see if I can do that, I'll submit it here if it works)
If you have a patch that makes using Log4J easier I would submit it directly through Bugzilla. I'm just a user, so the only thing I control is what goes into the tutorial initially.
Thanks for the tutorial, Ole!
Great to hear that you found it useful- Thanks, - Ole --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
