There are logging classes built into Java 1.4+. Here is how you use them:
Log4J allows channels to stream different classes of messages to different files, and to configure logging behaviour after the code is compiled on a very fine granularity.
Instead of peppering your code with debugging println statements that you remove entirely when you find the bug, with logging you leave the logging/generic debug instrumentation code in place and turn it on and off, in different parts of the program, to varying degrees of detail, at run time, without having to recompile. You normally leave at least a minimum amount of the logging engaged even in production to help track down trouble and to produce statistics.
Normally small project would not use a formal logging package, but almost any team project will be fitted with a logger.
|recommend book⇒The Complete Manual log4j
|The author is the creator of Log4J.
|Greyed out stores probably do not have the item in stock. Try looking for it with a bookfinder.
This page is posted
Optional Replicator mirror
Your face IP:[220.127.116.11]
You are visitor number