While debugging an application, to know the status of a java application at its execution time we use system.out.println(SOPL).
SOPL statements are printed on console, so they are temporary. It is not possible to store the SOPL messages in a permanent file/location.
In order to overcome the problems of SOPL statements Log4j came into picture, with Log4j we can store the flow details of our Java/J2EE in a file or databases.
Working with log4j is nothing but working with classes & interfaces given in org.apache.log4j.*
When the applcation goes live we can analyze the log files to find the actual reason of error. This helps us to find out if there was an error/exception in application or there some error/wrong input from user itself.
In order to overcome the problems of SOPL statements Log4j came into picture, with Log4j we can store the flow details of our Java/J2EE in a file or databases.
Working with log4j is nothing but working with classes & interfaces given in org.apache.log4j.*
When the applcation goes live we can analyze the log files to find the actual reason of error. This helps us to find out if there was an error/exception in application or there some error/wrong input from user itself.
No comments :
Post a Comment