dear Devs and all other interested parties,
there is a new Logger in town, ahem OJ. previous to our latest release i was
fed up with the patchworked logging within OJ and implemented the one Logger to
rule them all.
main goals are
- simplicity
- ease of use
- independence of a specific logging framework (API wise)
since OJ 1.9 it is there and i already moved all logging calls i could find in
OJ core to use it.
usage is as simple as (logging class is autodetermined, no need to give it as a
parameter)
import com.vividsolutions.jump.workbench.Logger;
...
Logger.info("some info");
// or
Logger.debug("some debugging info", Throwable t);
// or for expensive operations you can do eg.
if (Logger.isTraceEnabled()){
// some expensive computing
Logger.trace("my expensive trace info")
}
see com.vividsolutions.jump.workbench.Logger for the avail methods.
stack traces are currently only shown when the log level is debug or up.
SETTING THE LOG LEVEL
1.
the log level can be given application wide as (new) OJ workbench argument
-v, -verbosity
logging verbosity, either: off, error, warn, info, debug, trace, all
2.
or as long as we are using log4j, in the log4j specific ways
- as java runtime parameters (-Dlog4j.debug etc.)
- in a log4j.configuration file, you can take the OJ default (etc/log4j.xml) as
an example
3.
in code (currently only application wide) eg. Logger.setLevel("debug");
hope you like it.. ede
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Jump-pilot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
