cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reinhard Poetz (JIRA)" <j...@apache.org>
Subject [jira] Created: (COCOON-1765) Logging
Date Thu, 02 Feb 2006 22:29:03 GMT
Logging
-------

         Key: COCOON-1765
         URL: http://issues.apache.org/jira/browse/COCOON-1765
     Project: Cocoon
        Type: New Feature
  Components: - Blocks Framework  
    Reporter: Reinhard Poetz


[...] But my main thoughts is that logging need to be a centralized service, common for all
blocks (separate logging solutions for each block would be a pain).

The logging implementation is contained in a block (that is installed early) and makes the
logger available as a service that other block can get through the service manager. This way
the logging implementation is chosen by the choice of logging block. Observe that I only is
talking about the blocks fw, within a block an ordinary ECM can be set up and it will inject
the logger in its managed objects through the usual Avalon style.

Using the same logger interface everywhere is also practical I guess we continue to use the
o.a.avalon.framework.logger.Logger one. 

(by Daniel Fagerstrom: http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=113889468124728&w=2)

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message