Re: [displaytag-devel] Log4j

Luiz-Otavio Zorzella Wed, 05 Mar 2003 11:52:53 -0800

Ben,

it's not that I'm not too much of a fan of step debugging, or do not know how to run the "I-need-100Gb-1GHz" eclipse... But there is nothing permanent about this debugging -- as opposed to debugging messages placed in appropriate places in the code, where other developers will benefit from it (even when not running the app within an IDE).

But you do bring a point I was forgetting about -- exception logging. I intend to introduce a new feature so the user may turn on a "survive" mode for the tag, where, if there is an problem (exception) while fetching a property, the system will not simply die, as it does today (if the feature is on, of course), but rather continue (after "logging" that to the user through the logging API).

In whichever case, a logging API is, IMHO, one of the most important things to have...

And, BTW, all is only meant for after the release, of course...

Zorzella

Benjamin Simpson wrote:

It sounds to me like the decision to permit developer logging has been made.
Frankly, I think logging for debug purposes is a bad idea.   Perhaps
Zorzella needs to get an IDE and set a few server side breakpoints.

It was my understanding that nothing was going to be added except for
critical bug fixes.  Future additions would be made after a consensus has
been reached on what we would like to do with Ed's library.

Am I missing some channel of communication here?

Ben Simpson

----- Original Message -----
From: "Luiz-Otavio Zorzella" <[EMAIL PROTECTED]>
To: "Matt Raible" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, March 05, 2003 2:13 PM
Subject: Re: [displaytag-devel] Log4j

Matt,

I usually declare it static, so a single instance is ever created:

private static Log log = LogFactory.getLog(ParentDAOHibernate.class);

Ans I'm 100% ok with commons-logging as well...

In regards to purpose (another post) these should be mostly for
debugging the development of the display tags.

Zorzella

Matt Raible wrote:

I agree - commons-logging is much easier to write too. Then you can just
put a log4j.properties (or .xml) file + log4.jar in your classpath and
commons-logging with automatically recognize it.

The question is - how do we do it?  I usually do it on a class level and
make it static when needed.  Example:

private Log log = LogFactory.getLog(ParentDAOHibernate.class);

Matt

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Joseph Ottinger
Sent: Tuesday, March 04, 2003 6:10 PM
To: Luiz-Otavio Zorzella
Cc: [EMAIL PROTECTED]
Subject: Re: [displaytag-devel] Log4j


I wouldn't care to see Log4J dependency, primarily because
Log4J is so much larger than displaytags. If you really
really really want to tie displaytags to a logging framework
of some kind (which I'd advise against), go for
commons-logging, as it's far smaller and is a front for JDK
1.4's logging, LN2, and log4j as well.

On Tue, 4 Mar 2003, Luiz-Otavio Zorzella wrote:

Hi,

the display tag library is entirelly lacking logging messages -- I
wish to know if anyone objects to my adding a log4j dependency to
it...

Zorzella

-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The
debugger for complex code. Debugging C/C++ programs can leave you
feeling lost and disoriented. TotalView can help you find your way.
Available on major UNIX and Linux platforms. Try it free.
www.etnus.com _______________________________________________
displaytag-devel mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel


---------------------------------------------------------
Joseph B. Ottinger                 [EMAIL PROTECTED]
http://enigmastation.com                    IT Consultant

-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of
TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you
feeling lost and
disoriented. TotalView can help you find your way. Available
on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
displaytag-devel mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The

debugger

for complex code. Debugging C/C++ programs can leave you feeling lost

and

disoriented. TotalView can help you find your way. Available on major

UNIX

and Linux platforms. Try it free. www.etnus.com
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel

-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The

debugger

for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel

------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ displaytag-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel

Re: [displaytag-devel] Log4j

Reply via email to