directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Created: (DIRSEDA-11) Remove dependency on commons-logging
Date Tue, 21 Sep 2004 14:59:37 GMT
Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSEDA-11

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRSEDA-11
    Summary: Remove dependency on commons-logging
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Seda Framework

   Assignee: 
   Reporter: Alex Karasulu

    Created: Tue, 21 Sep 2004 7:59 AM
    Updated: Tue, 21 Sep 2004 7:59 AM

Description:
There are a bunch of LoggingXxxxxMonitor implementations that log monitor events using commons-logging.
 These classes are NOT used in any of the POJO's but as monitors they can be set on the POJOs
to log events.  

A Java application serving as a harness for protocol developers using our SEDA framework will
use these logging monitors.  The trivial usage of logging here in printing to the stderr is
something that we could easily implement without introducing the CL dependency which is a
concern in the community.  Here's an email trail where there were discussions on this topic.
 The final conclusion was to just implement a simple console logger rather than have the CL
dependency.

So what needs to be done is the removal of all CL deps in all monitors.  Plus when using the
commons-threadpool we need to implement our own logging monitor rather than using the one
for CL.

Good luck,
Alex



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

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

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


Mime
View raw message