"Mark Lybarger" <[EMAIL PROTECTED]> writes:
>we're looking to upgrade to turbine 2.3. seems the logging is quite an overhaul. is
>it common/possible to put the commons-logging logger instanciation in a base action
>or base screen class to reduce the code changes? if so could anyone mind a sample or
>such.
put
protected Log log = LogFactory.getLog(this.getClass());
in your base class and use log.debug(xxx) on all extended
screens. Your log messages will have the correct class name
prepended. I do this all the time.
In fact, if you extend VelocityScreen, you don't even have to do
this. There is a protected log object around (coming from
TemplateScreen).
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honourable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
