geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (GERONIMO-31) Specialized LogFactory
Date Wed, 27 Aug 2003 21:28:15 GMT
The following comment has been added to this issue:

     Author: Dain Sundstrom
    Created: Wed, 27 Aug 2003 4:27 PM
I don't think this is what we want to do.  Instead of wrapping the commons LogFactory, I think
we should write a log management service.  This service would tell tell commons-logging to
use our log implemenatation, although this is not currently possible I hope they patch the
system to set a specific logger after the system is running. Then this service could expose
the CacheLog4jLog service methods and Log4j operations like 'reload the configuration file'.
View the issue:

Here is an overview of the issue:
        Key: GERONIMO-31
    Summary: Specialized LogFactory
       Type: New Feature

     Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

    Project: Apache Geronimo

   Reporter: Brent Worden

    Created: Wed, 27 Aug 2003 3:37 PM
    Updated: Wed, 27 Aug 2003 3:40 PM

Replacement for org.apache.commons.logging.LogFactory.  It defaults
to creating org.apache.log4j.Logger objects, wrapped in
org.apache.geronimo.common.log.log4j.CachingLog4jLog objects.

I've added files where appropriate to utilize this factory in geronimo.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message