[ISSUES] Closed: (JLCP-127) Convert JLCP to use Log4j instead of printStackTrace

[email protected] Thu, 29 May 2003 10:38:59 -0400 (EDT)
Newsgroups gmane.comp.java.javalobby.communityplatform
Message-ID <[email protected]>
Message:

   The following issue has been closed.

   Resolver: Matthew Schmidt
       Date: Thu, 29 May 2003 10:37 AM

Thank god that's over.  Everyone, *PLEASE* use Jakart Logging instead of printStackTrace.  Use log.fatal(e) for JLCPPersistenceException and HibernateExceptions.  log.error(e) for IOExceptions in servlets and JSP tags.  log.debug(string) for output that isn't shown by default and log.info(string) for info that is printed all the time.
---------------------------------------------------------------------
View the issue:

  http://jira.jlcp.org/secure/ViewIssue.jspa?key=JLCP-127


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JLCP-127
    Summary: Convert JLCP to use Log4j instead of printStackTrace
       Type: Improvement

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: Javalobby Community Platform
   Fix Fors:
             0.7.0 (Shiva)
   Versions:
             0.5.0 (Delorean)

   Assignee: Matthew Schmidt
   Reporter: Matthew Schmidt

    Created: Tue, 11 Mar 2003 1:50 PM
    Updated: Thu, 29 May 2003 10:37 AM

Description:
We need to go through and remove most of the printStackTrace and replace them with Log4J calls.  This will improve performance, because we've got too much output. 


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.jlcp.org/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira